[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <72dbd3150708271212w6bcca4c4web26d7cb25892afc@mail.gmail.com>
Date: Mon, 27 Aug 2007 12:12:06 -0700
From: "David Rees" <drees76@...il.com>
To: "Daniel Walker" <dwalker@...sta.com>
Cc: "Michal Piotrowski" <michal.k.k.piotrowski@...il.com>,
"Andrew Morton" <akpm@...ux-foundation.org>,
"Björn Steinbrink" <B.Steinbrink@....de>,
eranian@....hp.com, ak@...e.de, linux-kernel@...r.kernel.org,
"Natalie Protasevich" <protasnb@...il.com>
Subject: Re: Who wants to maintain KR list for stable releases? (was Re: nmi_watchdog=2 regression in 2.6.21)
On 8/27/07, Daniel Walker <dwalker@...sta.com> wrote:
> Now that I'm looking at the kernel bugzilla .. If you set the kernel
> version to 2.6.22 and set the "Regression" check box you could denote
> the fact that it's a regression in that kernel version ..
>
> I don't know if this URL is going to come out right,
>
> <snip url>
>
> That should be open bugs , kernel version 2.6.22, with the regression
> check box set ..
>
> So you may not need a master tracking bug ..
Yep, that's another way to do it. The method I described earlier is
commonly used when you don't have the handy regression field in
bugzilla. The technique is handy for creating lists for tracking other
types of issues which don't necessarily fall into a component and you
don't want to bother customizing bugzilla.
I also suspect that there will be a number of common searches that
many people will find useful. With recent versions of bugzilla (3.0+)
you can share searches within groups, but it may be helpful to have a
wiki or some other page where useful searches can be stored, or one of
the templates edited to include those common searches.
-Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists