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.
>Subject: any chance of 2.6.0-test*?
From: William Lee Irwin III <wli () holomorphy ! com>
>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
-- 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 shawn.starr@datawire.net "The power to Transact" - http://www.datawire.net- 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/