> As of http://www.fossil-scm.org/fossil/info/722d7cac97 Fossil records the > check-in time to the nearest millisecond. This should solve your problem > for now -- until you try your script on a machine that is so fast that it > can do two commits within the same millisecond...
I'm just doing an update, and get: Autosync: http://r...@dev.ronware.org/p/reva Bytes Cards Artifacts Deltas Sent: 130 1 0 0 fossil: *** time skew *** server time differs by 67.1 seconds Received: 2838 61 0 0 Total network traffic: 351 bytes sent, 758 bytes received My server and the client machine are within one second of each other, and the ping distance between them is under 1.2ms (avg). And I have the very latest fossil, 8854d6b6 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
