git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Annoyance wrt ref@{1} and reflog expiry

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 19, 2020, 21:49 UTC
Message-ID
<xmqqblleg1z7.fsf@gitster.c.googlers.com>
In-Reply-To
<20200619203639.i5jto4i52ptsihrs@glandium.org>
Mike Hommey <mh@glandium.org> writes:
Show 7 quoted lines
>> Or we could change the lookup side to use the value of the ref
>> itself when asked for @{0}, and use the "old" side of the only entry
>> when asked for @{1}.  That way, we do not need to play games with an
>> artificial entry at all, which may be a better solution.
>
> Or more generally, use the old side from @{n} when asked for @{n+1} when
> there are only n entries in the reflog.
Yup, I agree that it is the natural consequence.
Previous: Mike Hommey
Message 6 of 6 in “Annoyance wrt ref@{1} and reflog expiry”
  1. Junio C HamanoJun 19, 2020
  2. Sergey OrganovJun 19, 2020
  3. Junio C HamanoJun 19, 2020
  4. Junio C HamanoJun 19, 2020
  5. Mike HommeyJun 19, 2020
  6. Junio C HamanoJun 19, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.