On 8/1/2014 12:48 PM, David Botham wrote:
.... I will also, regardless of where my canonical repo resides, I will continue to work from local clones and sync back to the canonical repo.
IMHO, as a seasoned user of fossil at least, you should always work from a clone. At minimum, that puts your valuable bits into *two* files. If that clone can be on a second hard drive, or in a second machine, or in a second location, all the better.
I don't know exactly how dropbox decides when to synchronize a file, but I imagine that the pattern of activity involved in pushing from your clone outside the box to the repo inside the box will usually result in dropbox taking its copy shortly after the push. Whereas, actively working from the repo in the box would be updating the repo more often and have an increased risk of dropbox wanting to touch the file *during* some activity. That is the case you really need to avoid hitting: push or pull against the dropbox copy while dropbox is using it for synchronization.
In the use case you describe, you are likely quite safe from that as long as you aren't making changes on both office desk and laptop simultaneously and forcing dropbox to reconcile conflicts between two independent modifications of the copy of the repo in the box.
If the terms of use work for you, than a valuable alternative would be to put a clone on ChiselApp [1] and have all your PCs autosync to that. Or operate your own server, with a pinhole punched in your firewall for it.
[1]: http://chiselapp.com/ -- Ross Berteig [email protected] Cheshire Engineering Corp. http://www.CheshireEng.com/ _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
