public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mikle Kolyada <zlogene@gentoo.org>
To: gentoo-dev@lists.gentoo.org, "Michał Górny" <mgorny@gentoo.org>
Subject: Re: [gentoo-dev] [PATCH] package.deprecated: Create initial template
Date: Thu, 05 Dec 2019 20:56:34 +0300	[thread overview]
Message-ID: <70EE934C-7EA4-4CE3-BBCA-96225E5468EC@gentoo.org> (raw)
In-Reply-To: <20191205160957.576971-1-mgorny@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]

+1

5 декабря 2019 г. 19:09:57 GMT+03:00, "Michał Górny" <mgorny@gentoo.org> пишет:
>Signed-off-by: Michał Górny <mgorny@gentoo.org>
>---
> profiles/package.deprecated | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
> create mode 100644 profiles/package.deprecated
>
>diff --git a/profiles/package.deprecated b/profiles/package.deprecated
>new file mode 100644
>index 000000000000..b4803a4ce68f
>--- /dev/null
>+++ b/profiles/package.deprecated
>@@ -0,0 +1,17 @@
>+####################################################################
>+#
>+# This file specifies packages that are considered deprecated (but not
>+# masked yet).  It will trigger pkgcheck warnings whenever other
>+# packages depend on them.
>+#
>+# When you add an entry to the top of this file, add your name, the
>date
>+# in the UTC timezone, and an explanation of why something is getting
>+# deprecated.
>+#
>+## Example:
>+##
>+## # Dev E. Loper <developer@gentoo.org> (2019-07-01)
>+## # This is no longer supported upstream, please switch to
>dev-foo/bar.
>+## dev-foo/foo
>+
>+#--- END OF EXAMPLES ---
>-- 
>2.24.0

-- 
Простите за краткость, создано в K-9 Mail.

[-- Attachment #2: Type: text/html, Size: 1492 bytes --]

  parent reply	other threads:[~2019-12-05 17:56 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05 16:09 [gentoo-dev] [PATCH] package.deprecated: Create initial template Michał Górny
2019-12-05 16:36 ` Alexis Ballier
2019-12-05 16:53   ` William Hubbs
2019-12-05 17:11     ` Alexis Ballier
2019-12-07 10:34       ` Joonas Niilola
2019-12-05 17:39   ` Michał Górny
2019-12-05 17:59     ` Alexis Ballier
2019-12-05 18:04       ` Michał Górny
2019-12-05 19:12         ` Gerion Entrup
2019-12-05 22:00         ` Alexis Ballier
2019-12-06  8:23           ` Tim Harder
2019-12-06  9:03             ` Alexis Ballier
2019-12-06  9:33               ` Tim Harder
2019-12-06 10:50                 ` Alexis Ballier
2019-12-06 15:41                   ` Matt Turner
2019-12-06 15:46                     ` Michael 'veremitz' Everitt
2019-12-06 16:28                       ` Mike Gilbert
2019-12-06 17:57                         ` Michael 'veremitz' Everitt
2019-12-06 16:29                     ` Alexis Ballier
2019-12-06 17:58                       ` Michael Orlitzky
2019-12-07  9:38                         ` Kent Fredric
2019-12-07  9:46               ` Kent Fredric
2019-12-06 11:33             ` Michał Górny
2019-12-06 11:45               ` Tim Harder
2019-12-05 16:39 ` Andreas K. Huettel
2019-12-05 16:46 ` Matt Turner
2019-12-05 17:56 ` Mikle Kolyada [this message]
2019-12-05 19:01 ` Alec Warner
2019-12-05 23:37 ` Aaron Bauman
2019-12-06  0:36 ` Chí-Thanh Christopher Nguyễn
2019-12-06  7:15   ` Michał Górny
2019-12-06  7:35     ` Tim Harder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=70EE934C-7EA4-4CE3-BBCA-96225E5468EC@gentoo.org \
    --to=zlogene@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=mgorny@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox