Intersting problem and an intersting patch. I currently can not fully understand, how this can happen, but the idea is not bad. I have to investigate this a little further. Can ouy send me the output of ssphys of one of these problematic files? I'm wondering how the ADD record is missing.
'ssphys info'? Attached. V1 of this file is also inaccessible in Sourcesafe.
Do you know, whether the missing files where part of the conversion?You can check that by calling "ss.exe physical $path/to/file" and then check for the physical name within your vss2svn logs. Is there probably only a missing recover somewhere along the lines?
Physical file names from both cases appear in the logs, with no obvious errors. The project with missing files is old enough that I'm satisfied with the latest version, so I didn't investigate. With a brief look, it appears that the affected files were added but never changed. (So I'm not loosing much in the way of history anyway.) The zero size file is a slightly odd practice, and I could see it as a valid exclusion in case VSS lost some data.
If you've got some specific test you'd like me to run, let me know.
vjiaaaaa.xml
Description: application/xml
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
