From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Cc: Gentoo ppc AT <ppc@gentoo.org>,
Gentoo ppc64 AT <ppc64@gentoo.org>,
Gentoo alpha AT <alpha@gentoo.org>,
Gentoo sparc AT <sparc@gentoo.org>, ia64 <ia64@gentoo.org>
Subject: Re: [gentoo-dev] About reducing or even removing stable tree for some arches
Date: Mon, 16 Feb 2015 10:09:26 -0500 [thread overview]
Message-ID: <CAGfcS_=EDwxoR81FJaKDO6ahmP5hmX2D74Cdt6+guKmrGuxJcA@mail.gmail.com> (raw)
In-Reply-To: <1424093690.27408.35.camel@gentoo.org>
On Mon, Feb 16, 2015 at 8:34 AM, Pacho Ramos <pacho@gentoo.org> wrote:
>
> The current policy of maintainers dropping keywords after 90 days is
> simply not applied because it leads up to that maintainer needing to
> kill himself that keyword and ALL the reverse deps keywords
A published script might ease that, especially with the move to git
(where that could be done in a single commit).
Another option is to just allow the keywords to be dropped without
fixing the reverse deps on those archs in these circumstances, though
that can be messier for users.
--
Rich
next prev parent reply other threads:[~2015-02-16 15:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 13:34 [gentoo-dev] About reducing or even removing stable tree for some arches Pacho Ramos
2015-02-16 15:09 ` Rich Freeman [this message]
2015-02-16 15:16 ` Pacho Ramos
2015-02-16 15:36 ` Anthony G. Basile
2015-02-16 15:59 ` Joshua Kinard
2015-02-16 23:28 ` Rich Freeman
2015-02-20 8:06 ` Christopher Head
2015-02-16 16:05 ` Pacho Ramos
2015-02-16 21:22 ` Anthony G. Basile
2015-02-16 22:45 ` Mike Gilbert
2015-02-16 16:37 ` William Hubbs
2015-02-17 4:49 ` Michał Górny
2015-02-16 22:47 ` William Hubbs
2015-02-18 3:11 ` [gentoo-dev] " Duncan
2015-02-18 9:25 ` Pacho Ramos
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='CAGfcS_=EDwxoR81FJaKDO6ahmP5hmX2D74Cdt6+guKmrGuxJcA@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=alpha@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=ia64@gentoo.org \
--cc=ppc64@gentoo.org \
--cc=ppc@gentoo.org \
--cc=sparc@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