On Mon, Jul 30, 2012 at 2:30 PM, Konstantin Khomoutov
> 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.
This is an issue when you are trying to access bare repo that is not
already synced from the other machine to local one. That may and
probably will destroy repository consistency.
The only solution that will allow one to use git repo (local or bare
as remote) is to use one block device file inside Dropbox folder and
mount it when needed and then unmount it to allow Dropbox sync it as
one and only one binary file. This case could be easy replaced by
zipped bare repository that will also work as expected. Thus the only
safe that is easy enough is to never use Dropbox to store git
repositories. Use github, your own hosted repo (e.g. use gitolite to
admin it), or just use bare repo stored somewhere on remotely accessed
machine via regular ssh.
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@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at