Re: [PATCH 3/3] prevent HEAD reflog to be interpreted as current branch reflog

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Feb 5, 2007, 11:11 UTC
Message-ID: <Pine.LNX.4.63.0702051208070.22628@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <8c5c35580702020302g46f71fe3o24d7dc9490192cab@mail.gmail.com>

Hi,

On Fri, 2 Feb 2007, Lars Hjemli wrote:

> I think the following makes perfect sense:
> 
>  "HEAD@{yesterday}" = current branch, yesterday
>  "@{yesterday}"     = detached head (no branch), yesterday

Okay, so you say "HEAD@{yesterday}" does _not_ give you what HEAD pointed to yesterday, but "@{yesterday}" does?

Instead "HEAD@{yesterday}" looks up what HEAD points to _now_, and _then_ goes back to yesterday, finding out what that particular branch pointed to then, _regardless_ what HEAD was then?

Oh my, that's convoluted.

Ciao, Dscho

$ 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.