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

From: Shawn O. Pearce <spearce@spearce.org>
Date: Feb 5, 2007, 11:21 UTC
Message-ID: <20070205112101.GC14234@spearce.org>
In-Reply-To: <Pine.LNX.4.63.0702051208070.22628@wbgn013.biozentrum.uni-wuerzburg.de>

Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

Show 15 quoted lines

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

Depends on your point of view:

  HEAD: 1) noun.  Synonym for the branch I am currently on.
  HEAD: 2) noun.  Synonym for the commit I am currently on.

Now that we can detach our HEAD anytime we want, I'm in the latter camp, and your (Dscho's) meaning for HEAD@{yesterday} and @{yesterday} makes perfect sense.

But I suspect most Git users are still in the former camp, as they haven't been exposed to the process (or need, or desire) to detach their HEAD...

-- 
Shawn.