On Thursday, 1 of May 2008, Adrian Bunk wrote:We don't need to. To be exact, we control what we merge and when. There's no rule saying that every patch has to be merged as soon as it appears to be ready for merging, or during the nearest merge window, AFAICS. This was an argument agaist starting a separate development branch in analogy with 2.5, IIRC, and I agree with that. Still, I think we don't need to merge patches at the current rate and it might help improve their overall quality if we didn't. Of course, the latter is only a speculation, although it's based on my experience. Thanks, Rafael --
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Andrew Morton | -mm merge plans for 2.6.23 |
| david | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| PJ Waskiewicz | [ANNOUNCE] ixgbe: Data Center Bridging (DCB) support for ixgbe |
| David Miller | Re: [GIT]: Networking |
