4 ms·
Thank you. A few different SVN -> Git migration tools failed to migrate a large legacy repo at a previous employer. I thought I was doomed to be stuck on subve
by eterm 4y ago
Thank you.
A few different SVN -> Git migration tools failed to migrate a large legacy repo at a previous employer. I thought I was doomed to be stuck on subversion forever.
It was GitHub's migration that finally worked and got us migrated across.
Funny we were only svn because I had previously been part of an effort to migrate them to svn when I'd joined a few years prior because before that they were using an old TFS system where developers would block each other by checking out files which would lock them for the whole repo.
I knew that switching immediately to git would have been too much of a culture shock so I got them over to a CVS where people could at least work independently first. ( I also have a soft spot for svn anyway, I think for many small teams it works just as well as git with fewer opportunities to shoot oneself in the foot. )
- vtbassmatt 4y agoFWIW we aren't planning to turn off Subversion import [1]. Only the two-way bridge where you could keep using `svn` against the Git repo. [1] https://docs.github.com/en/get-started/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer https://docs.github.com/en/get-started/importing-your-projec...
- edgyquant 4y agoIs SVN just not used really? Why not continue supporting (or even adding more) alternative version control systems?