Re: merge status

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Wed, 9 Nov 2005, James Bottomley wrote:
> 
> > If that keeps happening, I think I'll just make sure that I don't always 
> > merge on the last day or two. Just to make sure that submaintainers don't 
> > "game" the system the wrong way. Maybe my "two weeks" are sometimes just 
> > ten days long, who knows..
> 
> That's a nice theory, except that it's my contributors who drop me in it
> by leaving their patch sets until you declare a kernel, dumping the
> integration testing on me in whatever time window is left.

My point is that if that keeps on happening, then you miss the window, and 
are hopefully ready EARLY next time around, four weeks later, when the 
next window opens.

And if your submaintainers keep screwing _you_, then you tell them to stop 
it, and stop accepting their patches in that window, so that it's _their_ 
code that gets delayed, not yours.

The development SHOULD NOT happen during the merge window. The development 
should have happened in the tree you wait to merge /while waiting/ for the 
window to open.

If you're doing the development during the merge window, not only do you 
get in late in the window, you also do a hurried job and thus almost 
certainly have a worse process.

The whole point of having timely merge windows is that we _can_ just say 
"sorry, you missed the bus, wait for the next one".

And trust me, I _will_ say that. People always complain that I'm being too 
soft. Not so this time. If people miss the merge window or start abusing 
it with hurried last-minute things that just cause problems for -rc1, I'll 
just refuse to merge, and laugh in their faces derisively when they whine 
plaintively at me, and tell them there's going to be a new opening soon 
enough.

If two weeks of merge window is too short, maybe the four weeks _between_ 
the windows is long enough to sort things out.

		Linus
-
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/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux