9 ms·
Please don't ever do this, unless you wish to invite Dropbox's file syncing to destroy your repo. (See http://stackoverflow.com/questions/1964347/mercurial-and
by damncabbage 15y ago
Please don't ever do this, unless you wish to invite Dropbox's file syncing to destroy your repo.
(See http://stackoverflow.com/questions/1964347/mercurial-and-i-guess-git-with-dropbox-any-drawbacks http://stackoverflow.com/questions/1964347/mercurial-and-i-g... and http://stackoverflow.com/questions/1960799/using-gitdropbox-together-effectively/5193256#5193256 http://stackoverflow.com/questions/1960799/using-gitdropbox-... )
- eliben 15y agoThe top-rated answer there warmly recommends using Git on top of DB.
- damncabbage 15y agoYes. I'm sure it works for the common case. It's the edge-case problems outlined in the answers below it that worry me more. Going out on a limb: I'd assume that if you care enough about your data to version it in a git repo, then I'd also assume that you'd not enjoy it exploding because of a sync problem between two computers.