Yea, like many people in this thread. I'd just like to add, you don't have to block on migrating SVN history. It's actually enough to make sure that the SVN rep

Yea, like many people in this thread. I'd just like to add, you don't have to block on migrating SVN history. It's actually enough to make sure that the SVN repo remains accessible indefinitely (if there's nothing secret in it, making a tarball of the SVN repo is a fine way to avoid running a server). I don't go through historic code often enough that it would be annoying to find a different repo when I need it, and half the time people's git conversions don't let me make sense of "This fixes a regression in r1234." Of course, there are other options too, like migrating and then using replace, migrating and then rebasing, etc. I just want to point out that even the lowest effort option is valuable enough compared to throwing away history.