On Thu, May 01, 2008 at 12:39:01AM +0200, Rafael J. Wysocki wrote:That's very true IMHO and is the thing which has been progressively appearing since we merge large amounts of code at once. In the "good old days", something did not work, the first one to discover it could quickly report it on LKML : "hey, my 128-way sparc64 does not boot anymore, anybody has any clue", and another one immediately found this mail (better signal/noise ratio on LKML at this time) and say "oops, I suspect that change, try to revert it". Now, it's close to impossible. Maintainers frequently ask for bisection, in part because nobody knows what code is merged, and they have to pull Linus' tree to know when their changes have been pulled. That may be part of the "fun" aspect that Davem is seeing going away in exchange for more administrative relations. But if we agree that nobody knows all the changes, we must agree that we need tools to track them, and tools are fundamentally incompatible with smart human relations. Maybe we could slightly improve the process by releasing more often, but based on topics. Small sets of minimally-overlapping topics would get merged in each release, and other topics would only be allowed to pull fixes. That way everybody still gets some work merged, everybody tests and problems are more easily spotted. I know this is in part what Andrew tries to do when proposing to integrate trees, but maybe some approximate rules should be proposed in order for developers to organize their works. This would begin with announcing topics to be considered for next branch very early. This would also make it more natural for developers to have creation and bug-tracking phases. Willy --
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Andrew Morton | 2.6.25-mm1 |
| david | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
git: | |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| David Miller | [GIT]: Networking |
| Natalie Protasevich | [BUG] New Kernel Bugs |
