1 |
Hi! |
2 |
|
3 |
On Tue, 15 Feb 2011, Donnie Berkholz wrote: |
4 |
> On 09:10 Tue 15 Feb, Gilles Dartiguelongue wrote: |
5 |
> > Le lundi 14 février 2011 à 19:19 +0100, "Paweł Hajdan, Jr." a écrit : |
6 |
> > > On 2/14/11 9:13 PM, Samuli Suominen wrote: |
7 |
> > > > And http://bugs.gentoo.org/show_bug.cgi?id=349053#c1 ? I tried to |
8 |
> > > > provide a clue howto get usable p.keywords list easy. |
9 |
> > > |
10 |
> > > IMHO it's in the middle. I still have to do a manual step, but at least |
11 |
> > > it's pretty straightforward. Anyway, I think a list that can be blindly |
12 |
> > > copy-pasted makes things even easier. |
13 |
> > |
14 |
> > I don't think making a list for each arch is going to make anything any |
15 |
> > easier for maintainers requesting stabilization, which means those list |
16 |
> > we need more time to generate before being released. You just move the |
17 |
> > problem to another place. |
18 |
> |
19 |
> Why would you need to do that? Can't you just make a single list that |
20 |
> either has keywords for every arch or a ** ? Presumably every arch needs |
21 |
> a certain set of packages stable, and it doesn't matter if you |
22 |
> redundantly specify packages that are already stable. |
23 |
|
24 |
Yes it does. I for one just use the list, compile and test all |
25 |
the packages. If an entry is already stable, that effort is |
26 |
wasted. |
27 |
|
28 |
I think automatically generating per-arch lists and dumping them |
29 |
on the bug is a nice way to do it. Having a "tabled list" for use |
30 |
by the maintainer and then generating one comment per |
31 |
arch-specific list seems like a good idea to me. Yes it is more |
32 |
verbose on the bug, but that is a little price to pay, I'd say. |
33 |
|
34 |
Regards, |
35 |
Tobias |
36 |
|
37 |
-- |
38 |
printk(KERN_ERR "msp3400: chip reset failed, penguin on i2c bus?\n"); |
39 |
linux-2.2.16/drivers/char/msp3400.c |