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.
I would like to add here, that you could get a better result if you use
the following trick for the Archive/Restore cycle:
* trun back the time on a local computer to a date prior to the first
checkin in your database
* create an empty database
* set the time back to the real time.
* now run the Import of your archive on this created database.
The point is, that after the above steps you will have an archive, that
has a creation date prior to your archived files. In the conversion step
this will be recognized and hopefully the projects will go directly to
the correct places, instead to orphaned.
An explanation for the "success" for going through the archive/restore
cycle is, that the database will be cleaned and also renumbered. This
can help to sort out all possible quirks.
Dirk
_______________________________________________
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
