From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Revisions for USE flag changes
Date: Sun, 13 Aug 2017 12:12:39 -0400 [thread overview]
Message-ID: <dcd0a224-f00e-9e5e-53ef-30ed46ee2280@gentoo.org> (raw)
In-Reply-To: <20170813160625.GA29656@linux1.home>
On 08/13/2017 12:06 PM, William Hubbs wrote:
>
> There is a down side you didn't talk about -- more work for the arch
> teams and for us in terms of stabilizations.
>
> When we revbump, a new revision automatically gets ~ keywords on all arches
> unless we make an exception. If a revision changes iuse but could still
> be built with the stable tree, I would want to be able to commit this
> type of revision directly to stable.
>
I don't think you should be adding features and code to stable ebuilds
in the first place, but if you're going to do it, then I wouldn't let a
little -r1 on the end of the filename stop you =P
next prev parent reply other threads:[~2017-08-13 16:12 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 23:50 [gentoo-dev] Revisions for USE flag changes Michael Orlitzky
2017-08-12 0:45 ` Brian Evans
2017-08-12 0:59 ` Michael Orlitzky
2017-08-12 1:04 ` Michael Orlitzky
2017-08-12 1:11 ` Brian Evans
2017-08-12 8:39 ` Paweł Hajdan, Jr.
2017-08-12 9:58 ` Michael Orlitzky
2017-08-13 2:52 ` [gentoo-dev] " Duncan
2017-08-13 10:11 ` Michael Orlitzky
2017-08-13 10:18 ` M. J. Everitt
2017-08-14 1:34 ` Duncan
2017-08-16 20:12 ` Daniel Campbell
2017-08-18 14:50 ` Duncan
2017-08-13 5:01 ` [gentoo-dev] " Hans de Graaff
2017-08-13 10:38 ` Michael Orlitzky
[not found] ` <CAJ0EP42EaW8=dm0c26Gaij9gEAmTVHxiyp5+Hc_CYGzEypudsA@mail.gmail.com>
[not found] ` <CAJ0EP40yVVpLqHL5qVixxgvMmJc7ezRsn42qLoe621wS0KF-VA@mail.gmail.com>
[not found] ` <CAJ0EP43YbX-vA5cWcFm_Etin4H31Nq2s_xYsrTwuOK6LVyW+9A@mail.gmail.com>
[not found] ` <CAJ0EP42HkoYEkL1vt=Lyt-Dw-1XkdAXed8DrBp4oYB9j01+PKQ@mail.gmail.com>
2017-08-13 17:28 ` Mike Gilbert
2017-08-12 4:22 ` [gentoo-dev] " Michael Palimaka
2017-08-12 10:16 ` Michael Orlitzky
2017-08-12 10:58 ` Michael Palimaka
2017-08-12 10:32 ` Rich Freeman
2017-08-12 5:02 ` [gentoo-dev] " Hans de Graaff
2017-08-12 7:03 ` Michał Górny
2017-08-12 9:57 ` Michael Orlitzky
2017-08-12 10:04 ` Toralf Förster
2017-08-12 10:29 ` Rich Freeman
2017-08-12 11:05 ` [gentoo-dev] " Michael Palimaka
2017-08-12 11:18 ` Rich Freeman
2017-08-14 12:01 ` Jason Zaman
2017-08-16 3:22 ` Michael Orlitzky
2017-08-16 15:56 ` Duncan
2017-08-16 16:09 ` Rich Freeman
2017-08-17 4:27 ` Jason Zaman
2017-08-12 14:14 ` [gentoo-dev] " Michael Orlitzky
2017-08-13 2:32 ` [gentoo-dev] " Duncan
2017-08-13 10:08 ` Michael Orlitzky
2017-08-13 16:06 ` [gentoo-dev] " William Hubbs
2017-08-13 16:12 ` Michael Orlitzky [this message]
2017-08-14 16:29 ` William L. Thomson Jr.
2017-08-14 16:21 ` William L. Thomson Jr.
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=dcd0a224-f00e-9e5e-53ef-30ed46ee2280@gentoo.org \
--to=mjo@gentoo.org \
--cc=gentoo-dev@lists.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