[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6bffcb0e0708270435m1554bb72k7e0c287916d0f836@mail.gmail.com>
Date: Mon, 27 Aug 2007 13:35:42 +0200
From: "Michal Piotrowski" <michal.k.k.piotrowski@...il.com>
To: "Jeff Garzik" <jeff@...zik.org>
Cc: "Andrew Morton" <akpm@...ux-foundation.org>,
"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 27/08/07, Jeff Garzik <jeff@...zik.org> 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?
I have tried to track all regressions, but it is a lot of work, so I
center on development kernels.
There are two lists (both unmaintained)
http://kernelnewbies.org/known_regressions_2622
http://kernelnewbies.org/known_regressions_2621
If you compare them, you will see "New regressions (submitted after
2.6.21 a.k.a. for -stable team)" - a long list of problems reported
after 2.6.21 release. I really do not have time to track issues in
stable releases.
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@...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