Thus said "Andy Bradford" on 04 May 2014 22:44:21 -0600: > What have I missed? Perhaps with the per round-trip commit it is not > really necessary to also have a COMMIT if the network drops that is > implemented in [1317331eed]?
Ok, as it turns out, one potential resolution is to simply call fossil_fatal when autosync fails during update here: http://www.fossil-scm.org/index.html/artifact/f90dabeaf78a319b0b3b8791c0dded8d2f6170ec?ln=132 This does have one side-effect when autosync is enabled, but it does perhaps further distinguish update from checkout. The side-effect is that if we call fossil_fatal here, it seems that it will not be possible to update to a different revision than the current checkout while the network is down. It will be possible, however, to do a checkout (or if autosync is disabled, updates work). Andy -- TAI64 timestamp: 4000000053673bb2 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
