If only one computer is accessing the repository, then failure to lock may be ok. But you'll still need atomic rename etc. to work. I may be overly conservative, but I would not (and do not) allow anyone to access a repository (cvs, svn, git, whatever) over NFS, ever. My expectation is that multiple git processes on one machine with a repo on local disk works fine. If not it's a bug. When you add a remote FS you have to wonder if the unix filesystem sematics are preserved. Another approach would be cloned repositories that constantly pull from the main one or each other, and have people use those. That will get you delayed merge conflicts, but they might be useful as RO replicas.
Attachment:
pgpLhmmzd2wjk.pgp
Description: PGP signature