From: Aaron Bauman <bman@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] The changes about the stabilization process
Date: Sun, 25 Dec 2016 23:32:56 +0900 [thread overview]
Message-ID: <1C92DAB1-DC94-4716-8F53-7BB8AB23A427@gentoo.org> (raw)
In-Reply-To: <20161226014902.65176ad1@katipo2.lan>
On December 25, 2016 9:49:02 PM GMT+09:00, Kent Fredric <kentnl@gentoo.org> wrote:
>On Sun, 25 Dec 2016 13:41:29 +0100
>Agostino Sarubbo <ago@gentoo.org> wrote:
>
>> NOTE: I'm intending this message as a sort of announcement to invite
>everyone
>> to port their stable requests. I guess there isn't much to discuss
>here. If
>> you don't like some of the changes that have been done, please open a
>specific
>> thread about.
>>
>> Thanks.
>
>A quick rundown on attaching stabilization lists as files might be
>helpful,
>especially in regards to that flag having three states, the "undefined"
>state (ie: no such flag)
>, and both "-" and "+" states.
>
It is not necessary to use a file now. Just put the list in the "Atoms to stabilize" as described.
>Also steps to take in regards to getting a "Flags: sanitycheck-" report
>should be clarified.
>
>( I assume these will all be in the wiki, I'm just jotting them here
>under the
>presumption that the content of this email and its replies will be used
>as a baseline
>for the wiki )
Not an expert and Michael can clarify, but sanity check basically means repoman does not check out. That is, the developer did not provide a proper stable list or target and potentially breaks the stable tree.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2016-12-25 14:33 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-25 12:41 [gentoo-dev] The changes about the stabilization process Agostino Sarubbo
2016-12-25 12:49 ` Kent Fredric
2016-12-25 14:32 ` Aaron Bauman [this message]
2016-12-27 11:15 ` Kent Fredric
2016-12-25 19:55 ` Andrew Savchenko
2016-12-26 0:30 ` Michael Orlitzky
2016-12-26 7:49 ` Kent Fredric
2016-12-26 10:05 ` Andrew Savchenko
2016-12-26 13:13 ` Rich Freeman
2017-01-04 1:57 ` Andrew Savchenko
2017-01-04 7:09 ` [gentoo-dev] " Michael Palimaka
2017-01-04 7:11 ` M. J. Everitt
2017-01-04 9:07 ` Kristian Fiskerstrand
2016-12-28 9:57 ` [gentoo-dev] " Ulrich Mueller
2016-12-28 16:49 ` [gentoo-dev] " Michael Palimaka
2016-12-28 17:22 ` Michał Górny
2016-12-28 20:11 ` Ulrich Mueller
2017-01-02 16:51 ` Kent Fredric
2017-01-02 16:57 ` M. J. Everitt
2016-12-28 22:21 ` Jeroen Roovers
2016-12-28 22:31 ` Ciaran McCreesh
2016-12-29 15:44 ` Jeroen Roovers
2016-12-29 17:22 ` Ciaran McCreesh
2016-12-29 11:10 ` Ulrich Mueller
2016-12-29 11:31 ` Michael Palimaka
2016-12-29 12:08 ` Ulrich Mueller
2016-12-29 12:25 ` Kristian Fiskerstrand
2016-12-29 12:28 ` Marc Schiffbauer
2016-12-29 15:52 ` Ulrich Mueller
2016-12-29 19:51 ` Marc Schiffbauer
2016-12-29 21:53 ` Mart Raudsepp
2016-12-29 17:23 ` Ciaran McCreesh
2016-12-29 19:52 ` Marc Schiffbauer
2017-01-02 16:56 ` Kent Fredric
2017-01-02 17:49 ` Rich Freeman
2017-01-02 17:59 ` M. J. Everitt
2017-01-02 19:01 ` Rich Freeman
2017-01-02 23:27 ` Mart Raudsepp
2017-01-03 23:28 ` Kent Fredric
2017-01-03 23:48 ` Rich Freeman
2017-01-02 18:49 ` Ciaran McCreesh
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=1C92DAB1-DC94-4716-8F53-7BB8AB23A427@gentoo.org \
--to=bman@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