Prev: [PATCHv2] regulator: Get rid of lockdep warning
Next: rfkill sysfs ABI
From: Douglas Gilbert on 13 Mar 2010 15:30
Ray Lee wrote:
> 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.

Ray,
I'm sure that James will appreciate your insightful
advice. And Alan Cox is probably waiting for your
thoughts on the design of serial device drivers.

Amazing that after yet another Linus rant, people
crawl out of the woodwork to attack the victim.

Doug Gilbert


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
First  |  Prev  | 
Pages: 1 2
Prev: [PATCHv2] regulator: Get rid of lockdep warning
Next: rfkill sysfs ABI