Re: [PATCH] refspec: make @ a valid refspec

From: Felipe Contreras <felipe.contreras@gmail.com>
Date: Nov 25, 2020, 00:14 UTC
Message-ID: <CAMP44s2Yt_Vin1rLg-q9Jt8pA+bTDMjYbwSaGHZLgoNKL_nEvg@mail.gmail.com>
In-Reply-To: <xmqqk0uagxei.fsf@gitster.c.googlers.com>

On Tue, Nov 24, 2020 at 5:14 PM Junio C Hamano <gitster@pobox.com> wrote:

>
> Jacob Keller <jacob.keller@gmail.com> writes:

Show 12 quoted lines

> > However, @{0} *does* refer to what is currently checked out, which
> > would be head.. So in a sense @ meaning "the current branch" and
> > applying @{0} would always be HEAD, no?
>
> Not really.
>
> It happens to hold true for @{0}, because by definition you couldn't
> have been on a different branch than the current one when you made
> the topmost commit on the current branch.  For @{1} and higher, it
> is always "where was the current branch at N commits ago?" which is
> different from "where was the HEAD at N commits ago?", unless you
> always use a single branch and never switch away.

But @{0} is always the same as HEAD@{0}, which is always the same as @.

-- 
Felipe Contreras