From: Greg Troxel <gdt@ir.bbn.com>
To: Khawaja Shams <kshams@usc.edu>
Cc: git@vger.kernel.org
Subject: Re: Multiple clients accessing git over NFS
Date: Sun, 14 Nov 2010 18:46:40 -0500 [thread overview]
Message-ID: <rmipqu7lb8f.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <AANLkTinX-XR2TaZPGPeWyekMq3e8wEDkfcmi_o6pTvMK@mail.gmail.com> (Khawaja Shams's message of "Sun, 14 Nov 2010 15:40:33 -0800")
[-- Attachment #1: Type: text/plain, Size: 699 bytes --]
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 #2: Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2010-11-14 23:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-14 21:24 Multiple clients accessing git over NFS Khawaja Shams
2010-11-14 23:11 ` Greg Troxel
2010-11-14 23:42 ` Khawaja Shams
2010-11-15 0:32 ` Jonathan Nieder
2010-11-15 19:56 ` Jan Hudec
2010-11-15 20:44 ` Drew Northup
[not found] ` <AANLkTinX-XR2TaZPGPeWyekMq3e8wEDkfcmi_o6pTvMK@mail.gmail.com>
2010-11-14 23:46 ` Greg Troxel [this message]
2010-11-15 16:24 ` J. Bruce Fields
2010-11-15 1:26 ` Sitaram Chamarty
2010-11-16 13:47 ` Alex
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=rmipqu7lb8f.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=git@vger.kernel.org \
--cc=kshams@usc.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.