I have a large vss database to convert, and have been doing the following:
-Purging all of the vss deleted files. -Destroying unwanted directories/files -Archiving the desired top level directory -Restoring the archive into a new vss db. -Running the conversion from the "trunk" This all appears to work well, and I haven't noticed any conversion issues that don't also exist with a conversion without the archive/restore. But, as the conversion contains so many files it is difficult to review, and I may be missing some issues. Is this a bad way to run the conversion? I don't mind that all of the files are in the orphaned directory, then moved to the desired directory as the last revision. The archiving of the vss database seems to make for a cleaner and much smaller conversion. It seems as though even though files are destroyed, some still end up in the conversion unless the project is archived/restored, then converted. (I really need to look into this further, but that is definitely what appears to be happening at first glance.) Please let me know if this is a very bad idea, or if this process should be just fine. Thank you, Jon _______________________________________________ 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
