From: Jonathan Nieder <jrnieder@gmail.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:32:59 -0600 [thread overview]
Message-ID: <20101115003259.GC26104@burratino> (raw)
In-Reply-To: <AANLkTim1bUbofDzC5HJnB--0WkT45ewbWCa25RebEgae@mail.gmail.com>
Khawaja Shams wrote:
> I am still interested in knowing if git can handle multiple
> simultaneous pushes on the same repository without encountering
> corruption issues.
Yes, concurrent attempts to update a branch are serialized. (But
please don't ask me to answer about NFS semantics. See
http://stackoverflow.com/questions/750765/concurrency-in-a-git-repo-on-a-network-shared-folder
for some notes.) See the note about fast-fowards in the git push
manual for how integrity is preserved.
After reading that, you might wonder: if there are many, many clients
pushing to the same branch, how is starvation avoided? Good question!
It isn't. If you have so many clients wanting to push to a single
branch, I would suggest having a single person or a few people
maintaining it, pulling from others. Life will be better for many
reasons, especially quality control.
Hope that helps.
Jonathan
next prev parent reply other threads:[~2010-11-15 0:33 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 [this message]
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
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=20101115003259.GC26104@burratino \
--to=jrnieder@gmail.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.