git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Angelo Borsotti <angelo.borsotti@gmail.com>
Cc: marcnarc@xiplink.com,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	git <git@vger.kernel.org>
Subject: Re: push race
Date: Mon, 15 Oct 2012 14:58:02 -0400	[thread overview]
Message-ID: <20121015185802.GD31658@sigill.intra.peff.net> (raw)
In-Reply-To: <CAB9Jk9A8E57byg+1yzc22ByC_3VQd0j+HGu8Sj9121=LToopyg@mail.gmail.com>

On Mon, Oct 15, 2012 at 05:50:47PM +0200, Angelo Borsotti wrote:

> correct, there will be no file overwriting because no files are
> written on the work tree.
> I tried to follow the actions of the program, but did not quite catch
> the 6. you mention.

It is the "oldval" parameter to refs.c:update_ref. Or if you are using
the "git update-ref" plumbing, it is the "oldvalue" parameter.

-Peff

  reply	other threads:[~2012-10-15 18:58 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
     [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 [this message]
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=20121015185802.GD31658@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=angelo.borsotti@gmail.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=marcnarc@xiplink.com \
    /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).