On Mon, Jan 31, 2011 at 10:36:08AM -0500, Joshua Paine spake: > 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.
That's a bit pejorative and hyperbolic, don't you think? > > 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. > *snip* To be clear, this has nothing to do with multiple people accessing the repository over the network. The setup is that several directories are on a network share to be accessed from multiple machines by each admin/developer. User 'joe' has a laptop, a desktop, several VMs on his desktop, and a build server. The repositories are on a network share because he'll be working on different parts fo the code from different machines (especially the VMs). He's wants all of his changes to be visible *everywhere* at once instead of having to commit -> push -> pull/update. The same sort of setup exists for other users except that they use dropbox or unison to automatically sync those changes across multiple boxen and some of them have the same issue so it's, likely, not about locking or the share protocol. Thanks for the reply. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
