From: Duy Nguyen <pclouds@gmail.com>
Date: Sun, 19 Mar 2017 09:19:37 GMT
Subject: Re: [PATCH] rev-parse: match @{u}, @{push} and ^{<type>} case-insensitively
Message-ID: <CACsJy8CV=9PoH6QHCeznJ4DFLJN5w1a74X3f4raqrh4zBzCe4Q@mail.gmail.com>
In-Reply-To: <20170318223409.13441-1-avarab@gmail.com>

On Sun, Mar 19, 2017 at 5:34 AM, Ævar Arnfjörð Bjarmason
<avarab@gmail.com> wrote:
> diff --git a/Documentation/revisions.txt b/Documentation/revisions.txt
> index ba11b9c95e..55bde6ea65 100644
> --- a/Documentation/revisions.txt
> +++ b/Documentation/revisions.txt
> @@ -96,7 +96,8 @@ some output processing may assume ref names in UTF-8.
>    refers to the branch that the branch specified by branchname is set to build on
>    top of (configured with `branch.<name>.remote` and
>    `branch.<name>.merge`).  A missing branchname defaults to the
> -  current one.
> +  current one. Both '@\{upstream\}', '@\{u\}' are case-insensitive, so e.g.
> +  '@\{UPSTREAM\}', '@\{U\}' or '@\{Upstream\}' also work.

Since this change makes @{everything} case-insensitive and there's no
new one on the horizon, can we just say "everything in @{..} is
case-insensitive unless otherwise specified" and not updating every
@{case}? It sets a new common rule for these @{}, which I think is
good (easier to remember as a user).
-- 
Duy