* Chuck Ebbert <cebbert@redhat.com> wrote:

quoted text
> > it's a 2.6.24.1 candidate i believe. We trigger plenty of various 
> > crashes during x86.git maintenance and others hit various crashes in 
> > -mm, so by the time .1 is released we'll have it in .25 and can 
> > backport it. Most folks/distros will update to 2.6.24.1 very quickly 
> > so there's no risk of months loss of quality to kerneloops.org data 
> > either.
> 
> Using the same logic, why not put it in 2.6.24 and then remove it in 
> 2.6.24.1 if it's broken?

hm, did you understood my .25 reference to mean 2.6.25-final? I meant 
2.6.25-rc1. Or if there's a 2.6.24-rc8 planned then we could put it in 
right now [with the bisectability fixes, i.e. not the original series]. 
I.e. IMO what we shouldnt do is to put in these fixes without having had 
_some_ -rc release inbetween.

	Ingo
--
unsubscribe notice
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/