Just read your message again--I think you indicated that you're sharing a single working copy over the network. That's kind of crazy, and not at all recommended.
Assuming the issue I mentioned in my last doesn't apply to you because your network file system protocol is more robust, you'd normally do something like this: $ fossil new /net/fossil/myrepo.fossil # create repo $ cd ~/my-working-copy $ fossil open /net/fossil/myrepo.fossil Now suppose that your coworker has the same network share mapped to /share instead of /net on his system, and he wants to call his project folder someing different than you did. No problem! On his machine he would do: $ cd ~/project-name $ fossil open /share/fossil/myrepo.fossil You should now both be able to use your local working copies without a problem--or so I would expect. If this is the pattern you're using now, and you're getting the problems you mentioned, then you should each have a local copy of the repo cloned from and synced with a central repo over http or ssh, which is the even-more-normal way to do it. Joshua Paine LetterBlock: Web applications built with joy http://letterblock.com/ 301-576-1920 _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
