On Friday, July 28, 2006 1:46 PM +0200 Dirk <[EMAIL PROTECTED]> wrote:
I tried this the first time last weekend with a VPN connection over an
ADSL2 link. It was a horrible experience. ssexp even needed 5 minutes to
come up with my current project.
I changed the time expression to this:
AND (ABS(? - timestamp) < 21600)
This matches anything within 6 hours, and eliminated all my orphans (about
30-40). (Well, I have 3 due to CP1252 characters in filenames, but I'll
tinker with ssphys to deal with that.) It might be useful to log any time
delta larger than 30 seconds just to see how bad it gets.
That leaves me with 3 files with differing content. Now I'll investigate
those to see why VSS and vss2svn come up with different results.
For anyone wanting to compare a VSS and SVN checkout, here's the command
line I use:
diff -r -x .svn -x vssver.scc -x mssccprj.scc project-vss project-svn >
t:\vss-svn-20060801.diff
This uses Cygwin diff and assumes that a VSS checkout was done to
project-vss and an SVN checkout to project-svn. It uses the exclude switch
-x to ignore the local version control management files during the compare.
t: points to my tmp share.
_______________________________________________
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
