Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756131AbXH0LmV (ORCPT ); Mon, 27 Aug 2007 07:42:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754681AbXH0LmO (ORCPT ); Mon, 27 Aug 2007 07:42:14 -0400 Received: from wa-out-1112.google.com ([209.85.146.183]:58072 "EHLO wa-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754356AbXH0LmN (ORCPT ); Mon, 27 Aug 2007 07:42:13 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=M2sfrbymPXtLkVEO9uwdsJO+2kp8xl0a8DdyxivpLB8UIILKcq0HX8pUkGwL83WBkFUqzMuMUAaD1rqo2IAXYvyzHr+hV5BerLYodTK4eVu8APv/kF4+zmcGPrWOJU8fgbNi0SvGcanPs/YSh3FV6gNagiRXPYqKTG+6OzBnrlo= Message-ID: <6bffcb0e0708270442oad445a6jfbcac7f0a2c1d525@mail.gmail.com> Date: Mon, 27 Aug 2007 13:42:12 +0200 From: "Michal Piotrowski" To: "David Rees" Subject: Re: Who wants to maintain KR list for stable releases? (was Re: nmi_watchdog=2 regression in 2.6.21) Cc: "Daniel Walker" , "=?ISO-8859-1?Q?Bj=F6rn_Steinbrink?=" , eranian@hpl.hp.com, ak@suse.de, linux-kernel@vger.kernel.org In-Reply-To: <72dbd3150708270111h7845b5eam2b1d6279a0e33900@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1186531609.22044.50.camel@imap.mvista.com> <20070808142059.GF30805@atjola.homenet> <1187628296.7732.14.camel@imap.mvista.com> <46CDE94A.7000600@googlemail.com> <1187904169.2435.83.camel@dhcp193.mvista.com> <46D21E8E.4000003@googlemail.com> <72dbd3150708270111h7845b5eam2b1d6279a0e33900@mail.gmail.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1452 Lines: 42 On 27/08/07, David Rees wrote: > On 8/26/07, Michal Piotrowski 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. This sounds pretty easy :), thanks. Unfortunately, Bugzilla is not a standard tool for handling bug reports. > > -Dave > Regards, Michal -- LOG http://www.stardust.webpages.pl/log/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/