On Mon, 4 Feb 2008 11:02:38 +0000 Russell King <rmk+lkml@xxxxxxxxxxxxxxxx> wrote: > I don't see any end to these bun fights at the start of the merge window. > I believe it's inevitable given the work flow that we're now using. I'm trying to find someone who will run an merged tree of all the subsystems (I dub it "linux-next"). Subsystem maintainers will put their 2.6.x+1 material into branches or quilt directories for that tree. Once that person is found and the system is up and running we can solicit testing of that tree - it's basically like -mm without the -mm bits. Obviously I'll be able to put a lot of -mm in there too (uml, fbdev, etc, etc). Right now, the merge practices of the subsystem maintainers will drive that person insane, so some pushback will be needed to make it practical. None of which is really relevant to your complaint. But if/when linux-next is running, we can do more things around it. One might be "if a non-bugfix patch wasn't in linux-next one week prior to 2.6.x, it doesn't get merged into 2.6.x+1". For example. - To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
