From: Bob Hiestand <bob.hiestand@gmail.com>
Date: Fri, 14 Nov 2008 22:44:46 GMT
Subject: Re: reflog delete results in reflog show strangeness?
Message-ID: <cc29171c0811141444t30a35c65se1319a63a5443354@mail.gmail.com>
In-Reply-To: <cc29171c0811141433t43d27c5gb57ca11d2ddb67cb@mail.gmail.com>

On Fri, Nov 14, 2008 at 4:33 PM, Bob Hiestand <bob.hiestand@gmail.com> wrote:
> I see a possible bug in the output of 'git reflog show' after using
> 'git reflog delete'.  Simple example:
>
> $ git init
> $ git commit --allow-empty -m 'root'
> $ git commit --allow-empty -m 'good'
> $ git commit --allow-empty -m 'bad'
> $ git reflog
> 996ca67... HEAD@{0}: commit: bad
> e431a20... HEAD@{1}: commit: good
> 992dd88... HEAD@{2}: commit (initial): root
>
> $ git reset HEAD^
> $ git reflog
> e431a20... HEAD@{0}: HEAD^: updating HEAD
> 996ca67... HEAD@{1}: commit: bad
> e431a20... HEAD@{2}: commit: good
> 992dd88... HEAD@{3}: commit (initial): root
>
> $ git reflog delete HEAD@{1}
> $ git reflog
> e431a20... HEAD@{0}: HEAD^: updating HEAD
> 996ca67... HEAD@{1}: commit: good
> 992dd88... HEAD@{2}: commit (initial): root
>
> In this listing, please note that, after the delete, the commit SHA
> shown as HEAD@{1} is that of the deleted reference (the bad commit)
> and does not match the reflog message, which has the expected value.

Sorry, forgot to add this:

$ git describe
v1.6.0.4-969-g58a38d0