On Fri, 27 Jul 2012 22:18:24 -0700 (PDT) Owen Densmore <[email protected]> wrote:
> I'm setting up a github repo and would prefer my local git file > system to be in my dropbox file system. > > Is there any reason this would be a bad idea? The chief reason this is a bad idea is that while Git uses standard OS syscalls to work with the filesystem underlying its repo and its work tree directory, its implementation is optimized for the case of these things being a "local" filesystem backed by a fast device, and more [1]. People have really bad peoformance with network-backed filesystems when it's not about managing a dozen files or so -- see [2] and [3] as an example. (This is actually a recurring problem: people are constantly trying to put a local Git repo onto a network-backed filesystem for unclear reasons.) On the other hand, Git is happy to use a (bare) repository as a remote repository. So I would recommend to keep your local repository on a local filesystem, and set up a bare repository on your Dropbox filesystem which you would then add as your remote repository. This surely complicates the workflow somewhat as you have to explicitly push your work to your Dropbox-backed remote each time you need to sync, but in return you will enjoy fast and glitch-free Git performance. 1. It also assumes the filesystem implements working locking (in the sense locking actually works, not just appropriate syscalls complete successfully). But this is only an issue when there are several people accessing the repo in parallel, so this requirements probably does not apply to your case. 2. http://www.mail-archive.com/[email protected]/msg02531.html 3. http://www.mail-archive.com/[email protected]/msg02565.html -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
