I've been using fossil for about two or three months now and sometimes I encounter the following situation:
>From machine A I commit and push my latest changes to the remote repository. Then I try to pull and update these changes to machine B. It looks as if pulling worked because I see no error message and the amount of received bytes is in the expected range. But then fossil update does nothing and when I look at the local repository on machine B with fossil ui, I don't see my latest changes. My next step is of course to check the remote repository in the web browser and there I do see my latest commit. When I clone the remote repository to machine B and open it, I get my latest files. What's more interesting is that I can now pull and update from this cloned repository into my old local repository (all on machine B). Also, doing another commit on machine A has, until now, always fixed the situation until it occurs again sometime later. The roles of machines A and B can change. That means sometimes I can't update on A what I committed on B. Today I tried pull/update also on another machine C that hadn't been updated for a couple of days. It pulled and updated to the version *before* the latest commit. Again, in the ui the latest version didn't show up. Regards Ralf _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
