On Tuesday, September 19, 2006 9:39 PM -0400 Toby Johnson
<[EMAIL PROTECTED]> wrote:
Is there any reason why we should even keep the time difference in there?
I only added it in the first place as an abundance of caution to prevent
mismatched parent/child entries.
The only scenario where I can imagine this happening are cases where for
some reason a child action was missing/corrupted, and so two parent
actions picked up the same child action, but the sanity checker should
catch this. And the timestamp wouldn't help in that case anyway.
I took out the timestamp and changed the MergeParent step to only consider
the zero element of the returned array, and this failed with a huge
mismatch in the resulting trunk HEAD. I backed out that edit, but I may
have just mis-coded the array indexing. I haven't seen any warnings
indicating multiple child matches, which is why I suspect a coding error.
_______________________________________________
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
