On Wed, 30 Apr 2008 13:31:08 -0700 (PDT) Linus Torvalds <torvalds@linux-foundation.org> wrote:Well. We'll see. linux-next is more than another-tree-to-test. It is (or will be) a change in our processes and culture. For a start, subsystem maintainers can no longer whack away at their own tree as if the rest of use don't exist. They now have to be more mindful of merge issues. Secondly, linux-next is more accessible than -mm: more releases, more stable, better tested by he-who-releases it, available via git:// etc. It should be very easy for developers to do their weekly "does linux-next boot" test. Plus, of course, people who complain about merge-window breakage only to find that the breakage was already in linux-next except they didn't test it will not have a leg to stand on. I feared that linux-next wouldn't work: that Stephen would stomp off in disgust at all the crap people send at him. But in fact it seems to be going very well from that POV. I get the impression that we're seeing very little non-Stephen testing of linux-next at this stage. I hope we can ramp that up a bit, initially by having core developers doing at least some basic sanity testing. linux-next does little to address our two largest (IMO) problems: inadequate review and inadequate response to bug and regression reports. But those problems are harder to fix.. --
| James Bottomley | [Ksummit-2008-discuss] Fixing the Kernel Janitors project |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| David Miller | Slow DOWN, please!!! |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | Re: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49 |
