On Fri, Apr 05, 2013 at 04:48:56PM -0600, Eric Sandeen wrote: > One thing led to another in poking around the code, and I realized > that while userspace has lots of code copied from the kernel, it > was last copied in 2008, in many cases. ;) > > What's the plan here, how are userspace & kernelspace to be kept > in sync? > > New features fairly obviously hit both, but what about bugfixes > that hit one codebase or the other? > > Is it clear (to anyone) which code needs to be synced? > > Should it be done as a wholesale sync-up/rebase from time to > time, or should commits be merged from one to the other? >
So having just had to bring back part of the free space cache code I'd say we just cherry pick stuff since it is a huge pain to just copy it over, especially when you start talking about the extent buffer stuff. If maybe we could seperate out the really kernel specific stuff (like the stuff that does the reading/writing or interfaces with vfs) and the btrfs specific stuff then maybe it would be good to keep them in sync. But honestly I think the core stuff is pretty solid right now so cherry-picking is probably our better bet. Thanks, Josef -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
