On Wed, Aug 21, 2013 at 8:49 AM, Chad Perrin <[email protected]> wrote:
> > > > That sounds familiar. For the record, let me say I never (ever) make > > branches; all work here is done on trunk. > > In the repository where a fellow developer and I have seen this problem, > there have been no intentional branches made, so add one to the numbers > for this condition of the problem arising. > > The sync protocol for Fossil ( http://www.fossil-scm.org/fossil/doc/trunk/www/sync.wiki) pays no attention to check-ins or branching or tags or any other structure in the repository. The sync logic looks at the repository as an unordered bag of artifacts and it tries to make both participating repositories have the same set of artifacts. It treats the artifacts as opaque binary blobs. So, whatever this bug is, I'm guessing it does not have anything to do with branching. FWIW, the --verily option to "fossil sync" causes both participates to send "igot" cards for every artifact they hold (which can be tens or hundreds of thousands of artifacts). This seems to be sufficient to get both sides back into sync with one another. The downside is that with hundreds of thousands of artifacts, sending all those igot cards takes a lot of network traffic. The bug must be in one of the shortcuts by which Fossil normally avoids sending its complete set of igot cards. -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
