> So for both -mm and for the ocfs2 team, leaving the patch in the ocfs2 git
> tree is the most convenient place for it.
Well, I don't think it matters much either way because we mostly test by
checking out of svn and buliding against -mm or patched distro kernels. I'd
leave the details up to you and Joel (who maintains our ocfs2 git) -- whatever
is easiest for you guys.
> Obviously, merging it into Linus's tree will fix up everyone's patching
> problems, but it has no users at this time...
So, speaking of which, are there any barriers to merging OCFS2 now? I think
Christoph's concerns (silly /proc files, vma walking, endian stuff) have been
addressed.
- z
-
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]
