Cherry Pick merges in svn are shown a git merges in git

[PeterGrandcourt]

Cherry Pick merges in svn are shown a git merges in git

[PeterGrandcourt]

The consequence of this problem is that the contents of a branch does not match the history of the branch.
I think this is a critical issue as if you cannot rely on branch history, and you care about branch history, then the converted repository is unusable.
If, on the other hand you don't care about history, then you don't need convert a repository with all its history.

For most people migrating svn, with a standard ( or relatively standard repository) svn git will be a better choice as that records the branch history correctly.

svn git however is problematic if repository is very big (it is quite slow) and if you have moved branches around (including moving trunk around) or just have a lot of branches then the follow parents (default behaviour) causes it to recurs the history until it finds the parent. If you have many branches, and a big repo then this takes a lot of time. Switching off follow parents causes means that branch history is not connected to branch-parent history.

svn-all-fast-export is a great tool, but this problem makes it unusable at the moment for some use cases and I hope this issue can be resolved.