To give you a quick rule of thumb, when to use which resume task:
1.) If you are working on the same archive all the time, the converter will extract all versions of your items into the vssdata cache directory at the last step. As long as you work on the same archive you can reuse the cache directory, even if the archive has changed in between. In most cases you can use "--resume --task INIT". This will keep the cache intact, but will run the conversion from the beginning.
2.) If you are sure, that you havn't modified your archive (or you don't want to convert your latests changes), you can resume from task BUILDACTIONHIST or IMPORTSVN depending on the modification. If you have performed any modification in the ActionHandler.pm, you must resume from BUILDACTIONHIST. In case you modified the Dumpfile code you can resume from IMPORTSVN
3.) Starting from MERGEPARENTDATA is necessary if you have modified the MergeParentData function in vss2svn.pl. This is always necessary if you see unmatched additions of files to projects due to a huge time difference. (Sorry, I can't remember the error message in this case)
4.) Rereading the current state if your VSS archive has changed can be done with LOADVSSNAMES
5.) Any time when you performed major modifications on the database layout or if you are in doubt, you should start from INIT
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
