On Thu, 1 May 2008, Jeff Garzik wrote:Yes, the "stuff" may be supposed to be stable. But the trees feeding it certainly are not. People are rebasing them etc, and it doesn't matter because I think linux-next starts largely from scratch next time around. I do agree. And maybe I should have made it clear that I think it's worth it to me only if it then means that the merge window can shrink. If I'd have both a 'next' branch _and_ a full 2-week merge window, there's no upside. Btw, it wouldn't be another tree to test, since it would presumaby be what 'linux-next' starts out from - so it would purely be something that doesn't have the constant re-merging of the more wild-and-crazy 'linux-next' tree. Linus --
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
| Justin Piszcz | exception Emask 0x0 SAct 0x1 / SErr 0x0 action 0x2 frozen |
| Heiko Carstens | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
git: | |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Frans Pop | svc: failed to register lockdv1 RPC service (errno 97). |
| Radu Rendec | htb parallelism on multi-core platforms |
