1 |
On December 25, 2016 9:49:02 PM GMT+09:00, Kent Fredric <kentnl@g.o> wrote: |
2 |
>On Sun, 25 Dec 2016 13:41:29 +0100 |
3 |
>Agostino Sarubbo <ago@g.o> wrote: |
4 |
> |
5 |
>> NOTE: I'm intending this message as a sort of announcement to invite |
6 |
>everyone |
7 |
>> to port their stable requests. I guess there isn't much to discuss |
8 |
>here. If |
9 |
>> you don't like some of the changes that have been done, please open a |
10 |
>specific |
11 |
>> thread about. |
12 |
>> |
13 |
>> Thanks. |
14 |
> |
15 |
>A quick rundown on attaching stabilization lists as files might be |
16 |
>helpful, |
17 |
>especially in regards to that flag having three states, the "undefined" |
18 |
>state (ie: no such flag) |
19 |
>, and both "-" and "+" states. |
20 |
> |
21 |
|
22 |
It is not necessary to use a file now. Just put the list in the "Atoms to stabilize" as described. |
23 |
|
24 |
|
25 |
>Also steps to take in regards to getting a "Flags: sanitycheck-" report |
26 |
>should be clarified. |
27 |
> |
28 |
>( I assume these will all be in the wiki, I'm just jotting them here |
29 |
>under the |
30 |
>presumption that the content of this email and its replies will be used |
31 |
>as a baseline |
32 |
>for the wiki ) |
33 |
|
34 |
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. |
35 |
|
36 |
-- |
37 |
Sent from my Android device with K-9 Mail. Please excuse my brevity. |