Thus said Matt Welland on Fri, 10 Apr 2015 11:16:32 -0700: > I myself prefer not to see additional info like this that can be > derived from querying the db added to the timeline. I'm keen to see > the work that Andy and Jan have done make it into the trunk and will > test it ASAP.
It's not yet merged to trunk, but I have borrowed from Jan's work and merged into the sync-forkwarn branch for what I think will provide a better experience (e.g. almost no false positives). I say almost none, because it's possible that if your sync is cut-off, you may end up with a node that has a fork which has already been merged, but for which you didn't receive the correction (what are the odds?). But on the whole, I think this is much more reliable: https://www.fossil-scm.org/index.html/info/d0e2f1bd3e71ebf6 Thanks, Andy -- TAI64 timestamp: 40000000552b46a9 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
