just for the record, I believe I encountered something similar:
I have a very simple setup: a remote (cgi-served) repo (acting
essentially only as a backup but publicly accessible) and _one_ local
clone where only _one_ user (me) does checkins (the owner of the remote
server _could_ clone/do checkins but he doesn't...). autosync is 'off'
right now, so I do the `sync/push' manually (by habit I use `sync'
although `push' would suffice since no one _ever_ does an independent
checkin to the server-side repo (no other clone, no local developer on the
server) and I do not expect "incoming" changes.
so what I have observed a week ago was some hickup (I don't recall what
exactly, either a failed `sync' or `push') and retried (probably at that
point `sync'). I then discovered a fork popping up in the timeline which,
moreover, confusingly was some ten days in the past (the timeline had
already progressed several commits after the fork).
I don't see any reason why (and any way how) this fork could have occurred.
maybe this additional observation helps to get this "missing commit"
phenomenon sorted out -- it really is a bit scary even if nothing really
bad is happening to the repo content.
if you want to have a look, the repo is freely accessible here:
http://j...@fossil.0branch.com/sd
(maybe the repo content is even of some interest to someone ...)
the fork in question is [a8cbddcfc3]. In the meantime I have closed it
explicitly and edited the checkin comment (the latter I did directly in
the server-side repo where I've chosen a different user name than for the
local clone). the original ci-comment was identical to that of
[efd8772a0b] (and it's diff vs. [88f8514b9f] is a subset of the diff of
[efd8772a0b] vs. [88f8514b9f]).
I could not make head nor tail of this. I also cannot rule out completely
that I am responsible for the fork (making some stupid error) but really
cannot imagine how and that it has nothing to do with the problems
discussed in this thread. but maybe it does ...
j.
On Thu, 24 Apr 2014 07:20:56 +0200, Andy Bradford
<amb-fos...@bradfords.org> wrote:
Thus said Michai Ramakers on Wed, 23 Apr 2014 18:34:32 +0200:
I have no clue on sync logic at all, but perhaps this helps: in all
cases I remember here (3 or so), when sync of commit on host A was not
seen during sync on host B, doing a dummy-commit on host A, then
pulling again on B, worked, i.e. last 2 commits from A were pulled.
This sounds almost identical to the problem that I described that is
caused by a failed autosync except there is no mention of fork
happening. The fork may or may not happen if the branches were
different. But, committing after a failed sync will certainly cause
another autosync and then the push with the new changes will cause the
missing content to show up.
Andy
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
