From: Jakub Narebski <jnareb@gmail.com>
Date: Fri, 02 Feb 2007 10:31:23 GMT
Subject: Re: [PATCH 3/3] prevent HEAD reflog to be interpreted as current branch reflog
Message-ID: <epv3r9$4f7$2@sea.gmane.org>
In-Reply-To: <7vmz3xoas9.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:

> "Shawn O. Pearce" <spearce@spearce.org> writes:
> 
>> Nicolas Pitre <nico@cam.org> wrote:
>>> The work in progress to enable separate reflog for HEAD will make it
>>> independent from reflog of any branch HEAD might be pointing to. In
>>> the mean time disallow HEAD@{...} until that work is completed. Otherwise
>>> people might get used to the current behavior which makes HEAD@{...} an
>>> alias for <current_branch>@{...} which won't be the case later.
>>
>> I happen to really like the fact that HEAD@{...} is an alias for
>> <current_branch>@{...}.
> 
> It is usually easier to type.
> 
>> But now that HEAD will soon be getting its own reflog, I guess I
>> better relearn how to type <current_branch>.  :-)
> 
> One thing that is certain is that master@{...} will mean the
> same thing no matter what happens to Nico's series -- it talks
> about where the tip of that particular branch was at any recent
> time.  Right now HEAD@{...} happens to talk about "the current
> branch" (and only the current branch) -- Nico's patch would
> change the semantics when/if it is merged.

Perhaps we should use @{...} to refer to reflog for HEAD, or use
yet another special notation?

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git