3 ms·
Honestly, I just keep my checked out copy in Dropbox. If it's something I feel like keeping private, I just don't push it anywhere. Even less effort involved.
by lysol 15y ago
Honestly, I just keep my checked out copy in Dropbox. If it's something I feel like keeping private, I just don't push it anywhere. Even less effort involved.
- pcl 15y agoIf you have a working directory checked out in ~/Dropbox, beware of multi-machine madness. I've run into issues with a git repo in ~/Dropbox + IntelliJ + multiple computers -- if you leave IJ running on a machine you're not using, it'll notice file changes and re-index things in git. This can, in turn, cause Dropbox to create conflicts, effectively corrupting your git repo. As a result, I tend to keep only non-Java (i.e., non-IJ) projects in ~/Dropbox. Run "find .git -name 'conflict'" in your working directory to see if this has happened to you.
- pcl 15y agoOops; formatting fail. Should be '<asterisk>-conflict', not just 'conflict'.
- ajross 15y agoI'm sure the point was that it was a shared repository among a private group, not a personal thing.
- nollidge 15y agoThat's not clear. Folks downthread are talking about corruption that often occurs as a result of sharing in Dropbox.
- mhartl 15y agoI used to do this, but I learned the hard way that it fails terribly when you're working on different branches on different machines.