On Thu, Apr 24, 2014 at 10:36 AM, j. van den hoff <veedeeh...@googlemail.com > wrote:
> 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. > It is indeed, but until we can see it happening we can only guess as to what might actually cause it :(. My setups are almost 100% identical to yours - CGI repos mostly used by one user (except that i use autosync because i forget to push if i don't). i've been using Fossil daily for over 6 years and haven't seen this happen even once. Enough people have, though, that it's obviously happening. 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'm wondering if perhaps your server had "system event" and the clock was skewed for a brief period. That's probably impossible to know for sure now. > 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 ... > It does indeed sound somewhat related. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
