lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <72dbd3150708270111h7845b5eam2b1d6279a0e33900@mail.gmail.com>
Date:	Mon, 27 Aug 2007 01:11:55 -0700
From:	"David Rees" <drees76@...il.com>
To:	"Michal Piotrowski" <michal.k.k.piotrowski@...il.com>
Cc:	"Daniel Walker" <dwalker@...sta.com>,
	"Björn Steinbrink" <B.Steinbrink@....de>,
	eranian@....hp.com, ak@...e.de, linux-kernel@...r.kernel.org
Subject: Re: Who wants to maintain KR list for stable releases? (was Re: nmi_watchdog=2 regression in 2.6.21)

On 8/26/07, Michal Piotrowski <michal.k.k.piotrowski@...il.com> wrote:
> 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.

Here's how to use Bugzilla to track regressions between different
kernel versions:

Create a 2.6.22 regression bug and a 2.6.23 regression bug. All
regression bugs which are 2.6.22 regression bugs should block the
2.6.22 regression bug. All regression bugs which are 2.6.23 regression
bugs should block the 2.6.23 regression bug.

For example, say your master 2.6.22 regression bug tracking bug is #1.
When someone comes and files a new bug #2 which is a regression of
2.6.22, make bug #2 block bug #1. Then it is easy to see to track all
the 2.6.22 regressions.

To make it easier to remember what bug number tracks regressions for a
specific kernel, use a naming convention to create aliases for those
bugs.

-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

Powered by Openwall GNU/*/Linux Powered by OpenVZ