Just thought I'd give you a heads up on another tool for migrating from SourceSafe to Subversion.
I didn't know about your version of vss2svn when I wrote my tool and I also picked what seemed the obvious name. I've since renamed my tool so as to try to head off any confusion. I'd be interested to know about how your software goes about performing the migration. I've written up a general page on migration on my web site where I discuss migration strategies and I'd like to include a proper description of vss2svn, but need to know some detail about the migration strategy used. The page can be found here: http://www.kirit.com/Moving%20from%20Visual%20SourceSafe%20to%20Subversion There is also a page where I describe how I solved many of the problems with trying to get the right history out of SourceSafe. It may make interesting reading. It would be interesting (to me at least) to know how many of the problems become moot when looking at the database itself rather than the information provided by SS.EXE. http://www.kirit.com/Moving%20from%20Visual%20SourceSafe%20to%20Subversion/sourcesafe2subversion%20Migration%20tool Kirit -- http://www.kirit.com/
_______________________________________________ vss2svn-users mailing list Project homepage: http://www.pumacode.org/projects/vss2svn/ Subscribe/Unsubscribe/Admin: http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org Mailing list web interface (with searchable archives): http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.user
