> first. So everyone who has been changing stuff which is outside their > area of responsibility and breaking other people's stuff would get to > see the consequences of their actions instead of Stephen and I bearing > the brunt of it all the time. > > > I fear we've reached the stage now where people are merrily merging > bright-and-shiny things into their local trees without giving much > thought at all to the consequences for others. Its not that simple. There are areas where the tree divides don't fit the coding divides. ttydev was horribly entwined with USB and there really wasn't a way to break that up at the time in question. Because -next tries to assemble all the trees based on Linus tree it can't cope with that case well at all and in fact there was some neccessary rule bending to make next work out where some of the ttydev work was done with ttydev on top of other subtrees. So at times it would be very helpful with -next to be able to do limited tree ordering. If I could have flagged tty as requiring USB first for example there would have been a lot less pain involved. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
