Dirk, did you ever figure anything out with Archive/Restore timestamps?
Yes and no. The problem is still the same. All archived versions are stored with the original timestamps. But it is very likely that the project into which the archive is restored is from a later date than the archive itself. There is no other information in the records, except the restore action itself.
So if we are going to reconstruct by timeline, we have no chance to get it "right" in the first place.
My goal for the converter is to import everything before the restore point into the orphaned directory and to move the files out of this place at the restore point. In the end, everything should be in the correct place, but the times before things can be different.
Another possible solution would be to search for restore actions and to promote them back in time, until we reach the earliest possible no conflicting point, but this would be very problematic.
I suppose as a last-ditch resort, we could have an option to subtract a specific value from all "project" timestamps and leave files alone. Or maybe some sort of preprocessor that made a pass through the VSS data, looked for cases of files created before their projects, then reset the timestamps of those projects to 1 second earlier than its earliest file's timestamp.
I think it would be better to have some kind of "overload" file to overwrite timestamps and other information on a per version basis.
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
