From: Harald Nordgren <haraldnordgren@gmail.com>
Date: Fri, 02 Oct 2026 13:57:45 GMT
Subject: Re: [PATCH v2] object-name: accept @{p} as short for @{push}
Message-ID: <CAHwyqnV4KzDvqeSt-t6NUyV8L3pkstdYNP9itNKLS2guQ0yJuQ@mail.gmail.com>
In-Reply-To: <81BD7B8C-6E7E-451A-9D48-49ABD5FA5F68@gmail.com>

> > +test_expect_success '@{p} is short for @{push}' '
> > +    test_config push.default current &&
> > +    test_config branch.topic.pushremote other &&
> > +    resolve topic@{p} refs/remotes/other/topic &&
> > +    resolve topic@{P} refs/remotes/other/topic
> > +'
> > +
>
> I don’t recall offhand if @{U} case-variant is supported, but I wonder
> if we might not want to preserve as many single-character shorthands
> as we can, since there are a limited number that are reasonable to
> type.
>
> If upstream already supports different cases, though, symmetry is probably best.

It surprised me too, but '@{U}' is actually supported already.


Harald