Kenneth Porter schrieb:
In my "trunk" project, here's the worst offender so far, at 54.3 hours:
This is hard to believe, that this is a real scenario. Not similarity in
the bit pattern, and I don't expect somebody waited for 54 hours for the
operation to complete. This is also more than the summer / winter time
shift, and I would also think, that nobody adjusted the timestamp on the
server during that action.
Have you looked in the "time flow" of the parent and child item? Are
they intact by them self? What does vss reports in this case for the
time stamp for both histories, parent and client?
Do you know which one is the correct time?
Did you run analyze at some point of time and one of the records is
actually broken?
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
