git-svn is not the right tool for one-time conversions of repositories. It is a great tool if you want to use Git as frontend for an existing SVN server, but for one-time conversions you should not use git-svn, but svn2git which is much more suited for this use-case.
There are pleny tools called svn2git, the probably best one is the KDE one from https://github.com/svn-all-fast-export/svn2git. I strongly recommend using that svn2git tool. It is the best I know available out there and it is very flexible in what you can do with its rules files.
If you are not 100% about the history of your repository, svneverever from http://blog.hartwork.org/?p=763 is a great tool to investigate the history of an SVN repository when migrating it to Git.
2
jlee
On
this seems to be because the default log-window-size is too small.
When you get error, from the new git repo, try running:
git svn fetch --log-window-size=4000
You can experiment with the actual number, but 4000 was the magic number for me.
git-svnis not the right tool for one-time conversions of repositories. It is a great tool if you want to use Git as frontend for an existing SVN server, but for one-time conversions you should not usegit-svn, butsvn2gitwhich is much more suited for this use-case.There are pleny tools called
svn2git, the probably best one is the KDE one from https://github.com/svn-all-fast-export/svn2git. I strongly recommend using thatsvn2gittool. It is the best I know available out there and it is very flexible in what you can do with its rules files.If you are not 100% about the history of your repository,
svnevereverfrom http://blog.hartwork.org/?p=763 is a great tool to investigate the history of an SVN repository when migrating it to Git.