Ingo Molnar wrote:
> it's also a lot less frustrating and a lot more enjoyable that way IMO.
> If it's 50 small patches, then so be it ... 50 patches only take ~2
> seconds more for me to apply to x86.git (which time is immediately saved
> by the vastly improved reviewability and testability of a 50 patches
> set), so dont worry about any overhead on the maintainers side. And
> you'll end up moving up on the v2.6.25 contributors top-list on LWN as
> well ;-) The worst aspect of it is writing up the 50 changelogs (i use
> pre-created templates for that) and figuring out how to script a
> patch-bomb to lkml. In every other aspect it's a win-win scenario for
> everyone involved.
Well, testing for bisectability requires compiling each patch as its
applied, which gets painful for something like this where any change
will rebuild the world. And dealing with patch conflicts caused by
changing early patches in the series is never fun.
But I'm refactoring the series into smaller pieces now. Knowing what
the outcome should look like, and there the pitfalls are, makes it
fairly easy.
J
--
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]
