From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Angelo Borsotti <angelo.borsotti@gmail.com>, git <git@vger.kernel.org>
Subject: Re: push race
Date: Mon, 15 Oct 2012 18:53:28 +0700 [thread overview]
Message-ID: <CACsJy8Aw1iM9BTqv4jmoEK+a1gzKUL0rfVGFsnebofd67LxZew@mail.gmail.com> (raw)
In-Reply-To: <vpqd30k806o.fsf@grenoble-inp.fr>
On Mon, Oct 15, 2012 at 6:05 PM, Matthieu Moy
<Matthieu.Moy@grenoble-inp.fr> wrote:
> Angelo Borsotti <angelo.borsotti@gmail.com> writes:
>
>> the push command checks first if the tips of the branches match those
>> of the remote references, and if it does uploads the snapshot.
>
> The update does two things: upload objects to the database, and then
> update the reference. Adding objects to the database does not change the
> repository until the objects are reachable from a ref. Updating the ref
> is usually done giving the expected old sha1, and locks the ref, so it
> can't change in the meantime.
>
> I don't know this part of the code very well, but check refs.c for the C
> part, and "git update-ref" for the plumbing interface.
I think it's lock_any_ref_for_update(), which is called inside
refs.c:update_ref().
--
Duy
next prev parent reply other threads:[~2012-10-15 11:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 9:14 push race Angelo Borsotti
2012-10-15 11:05 ` Matthieu Moy
2012-10-15 11:53 ` Nguyen Thai Ngoc Duy [this message]
[not found] ` <CAPc5daUon3eLTDT=3wo_=rTCJWVe=ufCvmSzrjD=0T17Dxkpqw@mail.gmail.com>
2012-10-15 11:50 ` Angelo Borsotti
2012-10-15 14:09 ` Ævar Arnfjörð Bjarmason
2012-10-15 14:13 ` demerphq
2012-10-15 14:29 ` Marc Branchaud
2012-10-15 15:50 ` Angelo Borsotti
2012-10-15 18:58 ` Jeff King
2012-10-15 18:56 ` Jeff King
2012-10-16 2:09 ` Shawn Pearce
2012-10-16 4:51 ` Jeff King
2012-10-16 5:15 ` Nguyen Thai Ngoc Duy
2012-10-16 5:37 ` Jeff King
2012-10-16 10:45 ` Nguyen Thai Ngoc Duy
2012-10-16 17:02 ` Jeff King
2012-10-16 17:21 ` Junio C Hamano
2012-10-16 17:25 ` Jeff King
2012-10-16 19:09 ` Junio C Hamano
2012-10-16 6:35 ` Angelo Borsotti
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=CACsJy8Aw1iM9BTqv4jmoEK+a1gzKUL0rfVGFsnebofd67LxZew@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=angelo.borsotti@gmail.com \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).