Another possibility would be, that the file was broken and that analyze fixed the files in a way, that it "removed" the problematic records by introducing a large
As I said, these files had errors a few years ago; we ran multiple rounds of 'analyze' and eventually switched to a different project directory in sourcesafe (which later got renamed back to the original.) During analyze runs one of the files still reports an error indicating early revisions will be unaccessible.
This is still strange. Esp. in case that he files where never changed, if they where added, but not deleted, they must be part of the converted archive. Have you checked, whether they come out in the orphaned cache?
I ran this to no avail: grep -i orphan vss2svn-dumpfile.dat What should I in fact be looking for? Justin Love Creative Electronics & Software 650 Sundown Road South Elgin, IL 60177 Phone (847) 695-0023 FAX (847) 695 0483 _______________________________________________ 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
