Thus said "j. van den hoff" on Wed, 02 Dec 2015 12:43:45 +0100: > so, if this is correct, the phenomenon -- and thus a bug known since > yesterday -- seems to persist in 1.34 or is this an invalid > conclusion?
The OP did not mention what version the Fossil server was running before he made sure both server and client were running the latest. If it can be caused to happen after using --verily to get all the content and after having upgraded the server, then it could potentially be said to persist. For the sake of remembering... the old sync problem was server side. Andy -- TAI64 timestamp: 40000000565f11fa _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
