On Wed, 02 Dec 2015 11:54:06 +0100, Richard Hipp <[email protected]> wrote:
On 12/2/15, j. van den hoff <[email protected]> wrote:
thank you. sorry if this has been discussed/explained before: this
means,
there still is demand for that option? why? is there still a bug out
there? because if not, it seems whatever `--verily' is doing here should
be done all the time in order to avoid incomplete syncs in the first
place?
There are no known bugs. --verily is a defensive measure in case some
currently unknown bugs appear in the future.
well, the OP reporting the sync failure yesterday (andy gibbs) stated:
"I am syncing with a single server, and I have made sure all the clients
have
the same fossil version as the server (actually I've upgraded them all to
the latest released version). ..."
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? of
course, it's good to know that `--verily' fixes it but it seems a quite
unfortunate situation that complete sync is not guaranteed without that
option. what harm (in times of sync time/network traffic) would it do to
make `--verily' the default action of sync?
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
