[EMAIL PROTECTED] wrote:
Thanks Toby.
Agreed re. keeping the VSS database around in read-only mode. That is
the approach that I have chosen.
Re. the RESTORE issue - I noticed that there is physical information
indicating when the restore is done. I think vss2svn could be made to
"back-track" through the parent projects starting from each restore,
and adjust their timestamps - or some other similar solution. However,
I think the problems with my VSS database are bigger than that, so I
haven't spent any more time on this solution.
Yes, that is the approach we would probably take if we were to attempt
fixing the RESTORE issue but realistically that issue is probably too
big for any of the current developers to spend time on.
toby
_______________________________________________
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
