Re: multi-project repos

From: Junio C Hamano <junkio@cox.net>
Date: Nov 18, 2006, 07:31 UTC
Message-ID: <7vvelddxcx.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <20061118060243.GB2125@spearce.org>

Shawn Pearce <spearce@spearce.org> writes:

Show 15 quoted lines

> Junio C Hamano <junkio@cox.net> wrote:
>> Shawn Pearce <spearce@spearce.org> writes:
>> > Although if you have reflog enabled on your current branch there
>> > is a 1 character shorter syntax:
>> >
>> > 	gitk HEAD@{1}..
>> 
>> Are you sure about this?  I've seen "next@{1}" to look at
>> history of the named branch, but never history of "HEAD".
>  
> Yes.  :-)
>
> If the ref name is a symref then we resolve the symref all the
> way down to the real ref before we open and walk the reflog.
> Therefore this works.

True, except if you did:

        $ git pull
        $ git checkout otherbranch
        $ git show HEAD@{1}

My real point was that I was wondering if it also makes sense for ref-log to record switching branches for the symref itself.

But after sending that message I thought about it a bit more and concluded that it is not an interesting information. It is more code that affects unrelated places even if we were to implement it and without real gain, so let's not log symref itself and keep the current implementation.