> The maintainer can alway push really new stuff into 2.7, and Linus can
> always refuse to take a feature into 2.7 until something else is fixed in
> 2.6. Looking at how hard people are working to backport things from 2.5 to
> 2.4 I have faith that extra effort will be taken.
People using the systems in production are going to care about stability.
People selling systems to people using them in production are going to care
about the stable series. This means most of the people who have day jobs
working with Linux at places like Red Hat and IBM.
Look at the pressure to get stuff into 2.4 when it's already in 2.5. Because
2.4 is what people are actually using, and 2.5 is really just for os
development and testing (and general playing with) at this point.
Looking at it another way, Kieth Owens writing kbuild 2.5 and pushing hard
for its inclusion didn't stop other people from patching the endless series
of bugs in the old one. Even when Kieth at least considered this
counterproductive.
Rob
-
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/