[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070827160916.GF4121@stusta.de>
Date: Mon, 27 Aug 2007 18:09:16 +0200
From: Adrian Bunk <bunk@...sta.de>
To: Jeff Garzik <jeff@...zik.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
Daniel Walker <dwalker@...sta.com>,
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 Mon, Aug 27, 2007 at 05:41:17AM -0400, Jeff Garzik wrote:
> Andrew Morton wrote:
>> What I'm concerned about is that regressions which we didn't fix are just
>> getting lost. Is anyone taking care to ensure that they are getting
>> transitioned into bugzilla for tracking?
>
> Maybe this was a dumb assumption on my part, but I thought regressions were
> getting rolled over into the next release's list, if they are not solved?
Judging from the regression lists and the regression reports we get
post-release both on lkml and in the kernel Bugzilla we have much more
than 100 unfixed regressions since 2.6.20 (plus regressions from older
kernels...).
Tracking that many regressions is one problem (although getting all bug
reports in Bugzilla would make this quite easy), but the bigger problem
is how to get them debugged and resolved.
> Jeff
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
-
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