On Mon, Feb 07, 2011 at 05:55:08PM -0500, Richard Hipp wrote: > I haven't done an official build of Fossil on a long while. So I'll try to > do one on Wednesday. Please let me know if you see any serious problems > with the current tip of trunk. > > Note that I am unable to reproduce the sync problem reported in > http://www.fossil-scm.org/fossil/info/fbea61caf0 despite considerable > effort.
Hello, it's me reporting this problem. We experience this in all our machines, which use fossil versions all from this year. We did not see any of this until we enabled the delta manifests, around december. We do not commit baseline manifests at will; it is fossil thinking it is time to do so. We use mostly linux x86_64, and also some cygwin fossil windows builds, at a commit rate of around 10 commits per day, with quite enough files: $ fossil ls | wc -l 2930 All coworkers experenienced this, all synchronising against a fossil served by cgi. The fossil server is not that new; maybe it dates from late november. Does it matter? It looks like all fossil 'clients' get always the changes on sync, but they are not considered in the checkin DAG. Only after 'rebuild' they become part of the DAG. Tomorrow I can try to reproduce this in a new repository. Who is here using delta manifests in their repositories? Anyone else? I know fossil-scm.org does not use delta manifests. Regards, Lluís. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
