However, this approach also exposes some data that is simply impossible to retrieve using ss.exe or the OLE API, such as recovering child items from a deleted project, or correctly recovering the history of a renamed item, especially if different items of the same name existed in the repository at multiple points in time.
Deletions and Renames where the primary reason, why I had chosen to look into the database format. The VSS toolchain didn't worked in a way to reveal the information. So it would be very interesting to know how you had solved this problem, and that is the most important question, whether the converted items are the correct ones. My experience was, that esp. in rename situations, and when an item with the same name was added later, VSS failed to retrieve the correct content.
For simple archives, where you don't have these scenarios, this is no problem. But most real, bigger archives, will show problems, that you can not solve with a simple ss history command.
Best regards 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
