From: "Shawn O. Pearce" <spearce@spearce.org>
To: Jan Zalcman <zalcman@9livesdata.com>
Cc: git@vger.kernel.org
Subject: Re: Atomicity of git-push operation.
Date: Wed, 23 Dec 2009 07:25:29 -0800 [thread overview]
Message-ID: <20091223152529.GC13762@spearce.org> (raw)
In-Reply-To: <4B32044A.7010601@9livesdata.com>
Jan Zalcman <zalcman@9livesdata.com> wrote:
> I have a simple question about "push" operation but I couldn't find an
> answer: is git-push (also with --tags flag) atomic ? Especially: if refs
> changing (during push) is atomic ?
Yes, its atomic, at the per-ref level.
If you push 3 refs, and one of them updates during the push, the
other two will push successfully, but the one that was updated will
be rejected.
--
Shawn.
prev parent reply other threads:[~2009-12-23 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-23 11:51 Atomicity of git-push operation Jan Zalcman
2009-12-23 15:25 ` Shawn O. Pearce [this message]
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=20091223152529.GC13762@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=zalcman@9livesdata.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 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.