Re: [PATCH] object-name: accept @{p} as short for @{push}

From: D. Ben Knoble <ben.knoble@gmail.com>
Date: Sep 30, 2026, 21:39 UTC
Message-ID: <CALnO6CBR0XJUJR=2e5kUM8Fk9aV5uz+QxajRpnFFVTEkFfJQ3Q@mail.gmail.com>
In-Reply-To: <pull.2431.git.git.1790797186658.gitgitgadget@gmail.com>

On Wed, Sep 30, 2026 at 4:06 PM Harald Nordgren via GitGitGadget <gitgitgadget@gmail.com> wrote:

Show 10 quoted lines

>
> From: Harald Nordgren <haraldnordgren@gmail.com>
>
> Typing "git log @{p}.." fails with "unknown revision", even though
> "@{u}" works as the short form of "@{upstream}". Users who reach for
> the one letter spelling of the push destination by analogy get an
> error.
>
> Accept "@{p}" wherever "@{push}" is accepted, in any case, just like
> "@{u}".

I've oft wanted this. Though, I don't have a `p = push` (or `p = pull`) alias set, because it could be short for either!

There's no "@{pull}", though, so that reasoning doesn't apply here.

I have to wonder if there's an older discussion around these notations that explains why one got shorthand and the other didn't?

-- 
D. Ben Knoble