Sorry for reacting so late, I didn't read the list carefully in the last weeks and my gmail filter somehow didn't trigger on that. On Tuesday 02 October 2012 16:20:22 Junio C Hamano wrote: > * fa/remote-svn (2012-09-19) 16 commits > - Add a test script for remote-svn > - remote-svn: add marks-file regeneration > - Add a svnrdump-simulator replaying a dump file for testing > - remote-svn: add incremental import > - remote-svn: Activate import/export-marks for fast-import > - Create a note for every imported commit containing svn metadata > - vcs-svn: add fast_export_note to create notes > - Allow reading svn dumps from files via file:// urls > - remote-svn, vcs-svn: Enable fetching to private refs > - When debug==1, start fast-import with "--stats" instead of "--quiet" > - Add documentation for the 'bidi-import' capability of remote-helpers > - Connect fast-import to the remote-helper via pipe, adding 'bidi-import' > capability - Add argv_array_detach and argv_array_free_detached > - Add svndump_init_fd to allow reading dumps from arbitrary FDs > - Add git-remote-testsvn to Makefile > - Implement a remote helper for svn in C > (this branch is used by fa/vcs-svn.) > > A GSoC project. > Waiting for comments from mentors and stakeholders. >From my point of view, this is rather complete. It got eight review cycles on the list. Note that the remote helper can only fetch, pushing is not possible at all. > > > * fa/vcs-svn (2012-09-19) 4 commits > - vcs-svn: remove repo_tree > - vcs-svn/svndump: rewrite handle_node(), begin|end_revision() > - vcs-svn/svndump: restructure node_ctx, rev_ctx handling > - svndump: move struct definitions to .h > (this branch uses fa/remote-svn.) > > A GSoC project. > Waiting for comments from mentors and stakeholders. This is the result of what I did when I wanted to start implementing branch detection. I found that the existing code is not suitable and restructured it. The main goal is to seperate svn revision parsing from git commit creation. Because for creating commits, you need to know on which branch to create the commit. While for finding out which branch is the right one, you need to read the complete svn revision first to see what dirs are changed and how. It is rather invasive and it doesn't make sense without using it later on. So I'm not surprised that you may not like it. Anyways it passes all existing tests (that doesn't mean it's good of course ;)) Florian -- 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