I also found an operation in my DB with parent/child pairs somewhat more than 6 hours apart (probably a clock setting error) so I bumped up the limit in the SQL WHERE clause to 2 days. This should cover both WAN delays and time zone issues (but not the issue of storing the right time values corrected for client time zone in the dump file).
Do you know, which of the two actions comes first, the Create or the Add? Normally I would think, that almost always the Create Action comes first. Only if the timeline is broken. So I'm thinking to not depend on this "merge" process anyway, but to handle the two actions separately in different ActionHandlers.
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
