From: Eric Sunshine <sunshine@sunshineco.com>
Date: Tue, 10 Sep 2013 22:51:28 GMT
Subject: Re: [PATCH v6 7/8] update-ref: support multiple simultaneous updates
Message-ID: <CAPig+cQ=PSQbF4+YfZC-Ps2Te47VNTRm_yDTVY48vGh4G2UFgQ@mail.gmail.com>
In-Reply-To: <74c081c4004f3a8afb38ab15aff7d3178de4a1f8.1378773895.git.brad.king@kitware.com>

On Mon, Sep 9, 2013 at 8:57 PM, Brad King <brad.king@kitware.com> wrote:
> diff --git a/Documentation/git-update-ref.txt b/Documentation/git-update-ref.txt
> index 0df13ff..0a0a551 100644
> --- a/Documentation/git-update-ref.txt
> +++ b/Documentation/git-update-ref.txt
> @@ -58,6 +58,58 @@ archive by creating a symlink tree).
> +option::
> +       Modify behavior of the next command naming a <ref>.
> +       The only valid option is `no-deref` to avoid dereferencing
> +       a symbolic ref.
> +
> +Use 40 "0" or the empty string to specify a zero value, except that

Did you want an 's' after the "0"?

0's
"0"s
"0"'s
zeros
zeroes

> +with `-z` an empty <oldvalue> is considered missing.
> +
> +If all <ref>s can be locked with matching <oldvalue>s
> +simultaneously, all modifications are performed.  Otherwise, no
> +modifications are performed.  Note that while each individual
> +<ref> is updated or deleted atomically, a concurrent reader may
> +still see a subset of the modifications.