Linus Torvalds <torvalds@transmeta.com> said:
[...]
> The _real_ solution is to make fewer fundamental changes between stable
> kernels, and that's a real solution that I expect to become more and more
> realistic as the kernel stabilizes. I already expect 2.5 to have a _lot_
> less fundamental changes than the 2.3.x tree ever had - the SMP
> scaliability efforts and page-cachification between 2.2.x and 2.4.x is
> really quite a big change.
As a (mostly) bystander to kernel development here in lkml I see that there
are largeish areas in the kernel where ancient legacy, old, and new
mechanisms coexist. How about going _just_ for a big spring cleanup (Yep,
it _is_ spring around here ;-) (including kbuild, CML2, cutting everything
over to tasklets, getting rid of legacy timers, go after the results of the
Stanford checker, make the kernel-janitors work overtime, ...), going for
2.6 in a short(ish) time, and leave 2.7 for really new stuff? It should be
easier to do new development on a more uniform base (besides, having to
remember several ways to do things and the ugliness of it all does detract
from the fun of kernel development, which is the central objective AFAIU).
It should also naturally cut down the time between new stable releases.
Just too bad Halloween is now past, the moaning here would have added to
the spirit ;-)
-- Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513 - 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/
This archive was generated by hypermail 2b29 : Fri Nov 30 2001 - 21:00:21 EST