Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Is there a way to migrate SourceSafe with HISTORY into SVN?

Is there a way to migrate SourceSafe with HISTORY into a SVN ?

Ideally I'd like to use VisualSVN Server, but I don't really want to lose my SourceSafe history. If I have to I will though.

like image 202
David P Avatar asked Jan 06 '09 17:01

David P


People also ask

How do I migrate an SVN repository with history to a new Git repository?

Prepare a migration environment. Convert the source SVN repository to a local Git repository. (Optional) Synchronize the local Git repository with any changes from SVN repository while developers continue using SVN. Push the local Git repository to a remote Git repository hosted on Azure Repos.

How do I move SVN code from github to history?

Migrate from SVN to Git with History and Branches You will now need to edit each author in the author-transformed. txt file to match the syntax you need for your Git author information. Now that you have your list of authors ready, you can run the import using git svn and specify the authors-transform. txt .

Which popular tool can be used to migrate SVN to Git?

There are many tools such as svn2git available to perform the migration, in this tutorial we will focus on git-svn utility: a Git extension , which can be used to check out a Subversion repository to a local Git repository and then push changes from the local Git repository back to the Subversion repository.


1 Answers

A long time ago (it seems) I tried to migrate a SourceSafe DB to subversion using vss2svn, but finally gave up. There were several problems, IIRC:

  • you have to make sure that the SS DB is consistent (e.g. Analyze does not find any problems or is able to fix them).
  • it took a very long time to migrate the DB, because it was quite big.
  • finally the migration failed due to some problems with parsing dates. I wasn't able to find the reason for the problem, but I guess it was due to the fact that we use DD.MM.YYY date format instead of US date format.

So finally we decided to keep the SourceSafe DB intact (read-only) and just migrate the current version into subversion. So far, there were very few occasions where we had to go back to SourceSafe to check something.

Hope this helps.

BTW: it does not matter whether you use VisualSVN Server or subversion directly (svnserver). The repository format is the same in both cases.

like image 179
M4N Avatar answered Oct 14 '22 05:10

M4N