York, William wrote:
> All,
>
>
>
> I have browsed the archives and have found the 3 different
> VSS2SVN scripts available at tigris.org. The one thing I wasn't able
> to find was a recommendation on which product will best convert our
> repository with the history intact . It looks like vss2svn is in a
> alpha state with development stopped in mid August, vss2svnmigrate
> doesn't keep history and vss2svn2 has the following line "Please see
> vss2svn <http://vss2svn.tigris.org/> for a much more mature but less
> complete migration tool." This really doesn't provide any clear
> guidance on if vss2svn or vss2svn2 will give me what I need. I was
> wondering what the users experience is with these tools. The sooner
> we can move this code from VSS into SVN the better. ;-)
>
If possible (meaning you have Perl and the appropriate modules installed
or can install them) use the latest version of vss2svn from the
repository. I was the original author of that program and have decided
to take a completely different approach that hopefully will work out
better (eventually).
In the meantime some users have contributed many fixes that I never got
around to "releasing" but which are in the "0.3-bugfix" branch. This
includes the issue where some commit messages get trashed. It also
allows you to restart if it fails in the middle, which is a *big*
headache solver if it fails after running for 12 hours. :)
I can't really speak to the "vss2svn2" project; I don't think they've
worked on it in a while. If you have more specific questions about
vss2svn before migrating, please go ahead and use that mailing list.
Received on Thu Sep 8 17:43:28 2005