Nick Piggin <[email protected]> wrote:
>
> Michael Thompson wrote:
> > On 5/12/06, Nick Piggin <[email protected]> wrote:
>
> >> BTW. I'm not sure if linux-fsdevel has different conventions; however
> >> usually you don't break up a patch according to files, but logical
> >> components or transformations from one "sane" kernel tree to the next.
> >> And that means things keep compiling and working.
> >
> >
> > The files themselves are broken down into logical components, so the
> > per-file patch approach seems reasonable to me.
>
> Half a filesystem is a logical component?
>
> At the very least it wires up all the kconfig stuff _first_, so it
> breaks the tree from about patch 3 until 13.
Doesn't matter. The rule is stated as "kernel should compile at each
step", but the _real_ rule is "don't break git-bisect".
Nobody is going to include a half-applied filesystem in their .config while
performing git-bisection, so it can go in in any order.
-
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]
