Re: Who wants to maintain KR list for stable releases? (was Re: nmi_watchdog=2 regression in 2.6.21)

Andrew Morton
2007-08-27T16:46:40Z

On Mon, 27 Aug 2007 09:26:48 -0700 Daniel Walker <dwalker@mvista.com> wrote:

> On Mon, 2007-08-27 at 00:51 -0700, Andrew Morton wrote:
> > On Mon, 27 Aug 2007 02:45:02 +0200 Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
> >
> > > Daniel Walker pisze:
> > > [snip]
> > > > Have you considered maintaining all the lists in Bugzilla?
> > >
> > > Yes, I have considered it.
> > >
> > > Bugzilla sucks when it comes to tracking things. There is
> > > a regression field, but there are no difference between
> > > 2.6.22 and 2.6.23 regression.
> > >
> > > Most people are reporting bugs through LKML:
> > > - 23 regressions with reference to LKML
> > > - 4 regressions with reference to Bugzilla
> >
> > Presumably that's fixable.
>
> I've got some addition grips that I just noticed ..
>
> http://bugzilla.kernel.org/show_bug.cgi?id=8945
>
> I just file the above bugz entry ..
>
> I know who caused the bug , Stephane Eranian <eranian@hpl.hp.com> ..
> However I can't assign the bug to him. The field was greyed out and
> forced the assignee as other_other@kernel-bugs.osdl.org ..
>
> I tryed to CC: eranian@hpl.hp.com , and it said "no match" .. I guess
> because he doesn't have an account.. So Stephane has no way to know the
> bug exists , other than me emailing him ..
>
> Also I couldn't check the "Regression" box until after I filed the bug..
> It would be nice to file the bug in one action if it's possible .. I
> don't know bugzilla well enough to know if that's possible tho.
>

It's a hassle when someone doesn't have a bugzilla account. But there are
humans sitting behind bugzilla handling stuff (fsvo "human"). I've already
forwarded your bugzilla report to Stephane pointing out that he doesn't
have an account.

I screen 100% of new bugzilla reports and for those which I think need
attention (most), I will ensure that the appropriate parties get to see the
report. I'll also verify that the "regression" state is correct and that
the provided info is sufficient-looking. (It's amazing how many people
have trouble with the "Most recent kernel where this bug did not occur:"
question).

What I haven't been doing is ensuring that the Product and Component fields
are suitably set. That's something which Natalie is now cleaning up.