On Fri, Mar 12, 2010 at 10:27 AM, James Bottomley wrote:I do always have a tree ready in the first days of the merge window. It
was, in fact, here:
[...]
The slight problem is that I accumulate updates (like almost everyone
else) from the few days before the merge window opened up until about
the middle of the second week. That's what goes into the final pull,
plus assorted bug fixes that showed up during the window.
You appear to being using git as a sort of baroque CVS. Fixes that
arrive after the beginning of the merge window should be put into a
separate branch other than the one ready for submission. Features that
arrive after the beginning of the merge window should be placed into
yet another branch destined for the next merge window.