* Alan Cox <[EMAIL PROTECTED]> [070404 17:42]: > > > That's only a problem when there are <too many> patches to be > > > reviewed. Hence, do more frequent postings of fewer patches per series. > > > That will likely also get you more reviewers. > > > > Yeah, I agree.. We've already missed two merge windows because of the > > large patch set :( The problem is that patch set just keeps growing. > > The other problem is that GIT patch sets are completely useless for > merging and reviewing if you simply fire off a blast of 70 changesets. > Each time you do it at least one gets queried or a NAK and the lot go in > the bin again. Repeat 50 times...
Yeah, it is also big pain to maintain patchset this large. > It would be enormously helpful if instead we got say 15 small patch sets > which are independant so that a query or NAK means 14 sets get applied > this time around not zero. I was thinking about merging the patches together more, but the end result would not be very readable, and we would lose the original author info. Also trying to do this 15 small patches at time would make it hard to have it all integrated within the two week merge window. It would be nice to get to a situation where we only have 10 - 20 small linux-omap patches ready for every merge window, and then send fixes during the -rc series. Regards, Tony - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
