Fossil: A decentralized version control, bug tracking, and wiki software
I&#x27;m reading the page on how the distributed bug tracking works.  I&#x27;ve heard of Fossil before but never dug too deeply.<p>&gt; But if a timestamp on a ticket change artifact is off by months or years, it can seriously confuse the replay algorithm for determining the current ticket state.<p>I understand the simplicity of merging all the ticket comments by timestamp, but couldn&#x27;t they at least include a reference to one or more recent comments to help establish order when clocks are off?  Still wouldn&#x27;t avoid intentional bad actors, but there are bound to be people with misconfigured clocks.<p>If I&#x27;m working on a Fossil repository and I want to see what bugs everyone else has reported, where do I go to get a list of other copies of the repository so I can query them for new bug reports?  Is there some kind of tracker that lists all the people currently publishing the same Fossil repository, so I can connect to each one and ask for updates?<p>I wrote a post [0] on my site about this concept recently.  It&#x27;s not really polished, I think the thoughts were incomplete.  It was written in the context of git due to its ubiquity these days, but the concept should apply the same to other DVCS.  I know I&#x27;m full of a lot of questions and few answers, but questions help me learn.<p>[0] <a href="https:&#x2F;&#x2F;www.gaxun.net&#x2F;ideas&#x2F;git-announce&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.gaxun.net&#x2F;ideas&#x2F;git-announce&#x2F;</a>