Hello Guillaume and Dave, thanks for sending your experiences. As we
have found from numerous user experiences, every case seems to be
different because VSS finds unique and interesting ways to corrupt
itself. :)
Most people find that creating and restoring a backup prior to
conversion will actually make the process more difficult. This is due to
the way VSS creates the timestamps when a restore is performed; it
appears that the contents of a folder were created after the folder
itself so there is no good way of determining where those files should
go. At least in this case it sounds like the history itself was
maintained even though they were considered "orphaned", so that's a good
thing.
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.
It may not be your preferred solution and I understand the frustration
in not being able to get a good conversion, but at least from personal
experience I can say that when we converted over, we ended up needing
the "old" history far less than we thought we would. So hopefully the
inconvenience is only temporary until you've been using SVN for a while.
Good luck,
toby
_______________________________________________
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
