Toby Johnson wrote: > Dave, even if you aren't able to get a near-perfect conversion, another > option is to convert as much as possible then overlay the "get latest" > on top and commit that. Another option that some end up using when they > can't get a good conversion is to just keep the VSS repo around in > read-only mode and start fresh in SVN.
Hello Toby, I would like to point out a third, intermediate, option that I ended up using : convert as much as possible into a *read-only* SVN repository, then do all new work in another, fresh, SVN repository. This gets us all the benefits of SVN for our historical data (better performance, "atomic" commits, "blame" functionality), while letting us define a clean new repository for new work. The only drawback is that when searching the history you have to switch repositories when you hit the cut-off point but in practice that's not such a big deal. Cheers, --Jonathan _______________________________________________ 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
