On Wed, Feb 1, 2012 at 8:03 AM, Leo Razoumov <slonik...@gmail.com> wrote: > On Wed, Feb 1, 2012 at 07:08, Richard Hipp <d...@sqlite.org> wrote: >> The clock according to the "D" card of the artifact. >> >> In other words, you can keep changing the value of a tag and the latest >> version always wins. >> >> If two people change the value of a tag while disconnected, then later sync, >> the latest change wins. > > Let say, the clock on your client machine is accurate but on my > machine the clock is one year behind (slight exaggeration-:). You set > a tag a month ago and I changed it today and then we sync. Your tag > still wins because my clock is hopelessly behind! The problem is that > D card value is set at the disconnected clients and there are no > guarantee that all these clocks are synchronized. Generally speaking, > one cannot rely on uncoordinated clocks to establish sequence of > events. I think that was one of the reasons git does not use > timestamps while building its DAG.
I was in a situation where this was happening regularly. I got warnings about the clocks being out of sync from fossil. I'm no longer in that situation (and traveling), so I can't easily test it, but isn't that still the case? <mike _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
