On Wed, Aug 6, 2014 at 3:25 PM, Stephan Beal <sgb...@googlemail.com> wrote:

> That's always been my assumption, but _somehow_ it avoids conflicting (if
> it sees a conflict, it creates two copies and lets the user sort it out,
> but i haven't seen that happen in about 4 years). My current hypothesis is
> that either the filesystem
>

Some background, potentially useful for David:

Back when i started using dropbox (very early on in their history), i did
indeed use it to host some of my proto-repos which hadn't earned a spot on
my web hoster. i would occasionally forget to enable dropbox on one machine
or the other, and dropbox would create a "conflict copy", but that was user
error and never led to corruption. i was always a bit nervous about hosting
repos there because:

a) trust issues related to locking (same thing Richard's talking about).
(That said, i have never been bitten in this regard in Dropbox.)

b) because Dropbox starts synching the sqlite temp files and whatnot unless
i pause syncing (which i then forget to re-enable, leading to conflict
copies). There's nothing fundamentally wrong with dropbox synching those
(as long as they don't conflict, and i never observed that happening), but
it's "the principle of the thing," in the same way that it annoys me to no
end when people double-click hyperlinks (causing the the web server just
got two requests for the same thing, one of which must be discarded (which
just bugs me)).

So i stopped using Dropbox for repo hosting (still use it for static repo
backups), but it wasn't due to real/observed problems, only out of concerns
over _potential_ problems. i.e. removing variables for the sake of repo
stability.


-- 
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to