any chance of 2.6.0-test*?
There will be a new kernel tree that will fit this purpose soon called -xlk (eXtendable or Extended Linux Kernel). The hope to make it an 'official' like -ac, -mm tree for stuffing experimental stuff into a post 2.6 (or just before 2.6 goes live) kernel. I will need help in getting this to become a reality in the coming months to 2.6.
The purpose of the tree is to get experimental code ready for the 2.7 (2.9?) tree. We want code that will add new drivers / devices and general improvements to the kernel. The goal is once these are stabilized they can be submitted to Linus and friends for blessings and inclusion into 2.7 dev *early* so we won't have a mad rush for features before the next feature freeze.
Quoted 1 line
Subject: any chance of 2.6.0-test*?
From: William Lee Irwin III <wli () holomorphy ! com>
Quoted 16 lines
Date: 2003-01-10 16:10:12
Say, I've been having _smashing_ success with 2.5.x on the desktop and on big fat highmem umpteen-way SMP (NUMA even!) boxen, and I was wondering if you were considering 2.6.0-test* anytime soon.
I'd love to get this stuff out for users to hammer on ASAP, and things are looking really good AFAICT.
Any specific concerns/issues/wishlist items you want taken care of before doing it or is it a "generalized comfort level" kind of thing? Let me know, I'd be much obliged for specific directions to move in.
Thanks,
Bill
Signature · 8 lines
Shawn Starr UNIX Systems Administrator, Operations Datawire Communication Networks Inc. 10 Carlson Court, Suite 300 Toronto, ON, M9W 6L2 T: 416-213-2001 ext 179 F: 416-213-2008 [email protected] "The power to Transact" - http://www.datawire.net
Quoted 5 lines · Shawn Starr
There will be a new kernel tree that will fit this purpose soon called -xlk (eXtendable or Extended Linux Kernel). The hope to make it an 'official' like -ac, -mm tree for stuffing experimental stuff into a post 2.6 (or just before 2.6 goes live) kernel. I will need help in getting this to become a reality in the coming months to 2.6.
The effort is really much better spent trying to get to 2.6 first before worrying about things like 2.7. I hope 2.6 doesn't turn into the "heres my 2.4+preempt+rmap patchset" monster that we saw six months ago.
Quoted 2 lines
We want code that will add new drivers / devices and general improvements to the kernel.
non-core changes (ie, new drivers) still get added during code freeze, and during 2.6.x, there's no need for a specific tree just for this. Adding a new driver doesn't (or at least shouldn't) impact any existing users if done right.
Quoted 4 lines
The goal is once these are stabilized they can be
submitted to Linus and friends for blessings and inclusion into 2.7 dev *early* so we won't have a mad rush for features before the next feature freeze.
Nice try. It'll still happen regardless. Bombing Linus with ten zillion patches when he opens up 2.7.x with "has been tested in 2.6-xyz" isn't the way to do it. Everything has to happen incrementally, or you end up with a mess.
Dave
Signature · 2 lines
| Dave Jones. http://www.codemonkey.org.uk | SuSE Labs
Quoted 5 lines · Shawn Starr
There will be a new kernel tree that will fit this purpose soon called -xlk (eXtendable or Extended Linux Kernel). The hope to make it an 'official' like -ac, -mm tree for stuffing experimental stuff into a post 2.6 (or just before 2.6 goes live) kernel. I will need help in getting this to become a reality in the coming months to 2.6.
Thanks, but please don't. The idea of the feature/code freezes, and then the stable version running alone for a while, is precisely to focus the hacker comunity on fixing the bugs and cleaning up, and then stabilizing the whole. Please don't distract them.
--
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