On Wed, Mar 09, 2011 at 06:10:17PM -0600, Jonathan Nieder wrote: > 2. Merge libgit2 into git.git: polish the existing code in libgit2 so > that standard git can use it. Presumably this would happen by > porting one function at a time, not by making git link to libgit2 > immediately. People familiar with libgit2 might be able to pick > out particularly interesting subsets to start with (diff > generation?). That's definitely bigger than a SoC project at this point. However, one smaller project might be to start implementing a subset of git commands (probably plumbing) on top of libgit2, and then see how well the result passes git.git tests. > 4. filter-branch killer: using fast-import's new features to implement > common filter-branch operations (--subdirectory-filter, > --prune-empty, obliterating certain files) faster. Yeah, I like that. Or maybe somebody can pick up git-sequencer, which in theory could be used to filter-branch, too (or maybe sequencer can go on top of fast-import? :) ). > 5. rev-list: Coping with timeskew. I don't think this is big enough for a SoC project. It's on my todo list for the near-term, though. > 7. packfilev4. I suspect that is too complex for a SoC project. But you never know. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html