On Sun, Aug 18, 2013 at 5:20 PM, Michai Ramakers <m.ramak...@gmail.com>wrote:
> 1) on host S: clone project from host S (http://S/my_repo) > 2) on host C: clone project from host S (http://S/my_repo) > 3) on host C: do some work, and commit changes > 4) on host S, 'fossil up' > 5) on host S: 'fossil timeline' doesn't show the recent commit > 6) on host S: 'fossil pull' doesn't show the commit either in 'fossil > timeline' > 7) on host C: do more work, and commit changes > 8) on host 'S': 'fossil up'; now all recent commits are seen > It sounds almost like you have autosync turned off - do 'up' and 'pull' show any network traffic? > - autosync=1 on both sides > But you've already verified that. > Related question: I typically use 'fossil up', and never 'fossil sync' > (or pull/push) in my workflow, working on 2 hosts on the same project > - should I? > That doesn't sound wrong. If autosync is on there is rarely a need for push/pull. Do an 'up' when you start working, to make sure you aren't working from what would become a fork, and it will sync/push when you commit (if autosync is on). i hope someone can help you resolve this - i also suspect that the problem will turn out to be something simple/silly. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
