On 5/11/06, Dirk <[EMAIL PROTECTED]> wrote:
Jon W schrieb: > The vss action was a delete (followed by a destroy a few months > later), and the svn action used was an "add" on 05/04/01 for both the > directory and files. > > Just let me know if you can think of anything that I should try or > lookup. I'll keep looking in the meantime. In case of a destroy you can't do anything. The file is really purged and there is no way to retrieve the state of the archive earlier than the destroy. Not in VSS and not in subversion. In VSS you can go back to each file and try to grep earlier version individually.
I should have been a bit clearer. Here is the basic order: $Source 05/04/01 12:44pm Renamed $Project to $Source $Project 05/04/01 1:08pm Added [ Shared files in $Source to $Project ] $Source 05/04/01 2:06pm Deleted $Source 06/06/01 3:00pm Destroyed So, the VSS database has each file's history in $Project from 1997, as the files were shared from $Source. Yet, the conversion has the Project directory and files "added" on 05/04/01. Rather than maybe doing a svn move of the files in order to save the file's previous history and file diffs. I thought that maybe since the "share" timestamps overlapped the delete of $Source that I could remove the $Source "delete" action (for which the same svn delete action would later reference the vss destroy action). However, this didn't help the conversion to keep all of the file history. It still thought that everything basically was added new on 05/04/01. -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
