reflog delete results in reflog show strangeness?

2 messages, 1 author, 2016-06-15 · open the first message on its own page

reflog delete results in reflog show strangeness?

From: Bob Hiestand <hidden>
Date: 2016-06-15 22:45:39

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.

Thank you,

bob

Re: reflog delete results in reflog show strangeness?

From: Bob Hiestand <hidden>
Date: 2016-06-15 22:45:39

On Fri, Nov 14, 2008 at 4:33 PM, Bob Hiestand [off-list ref] 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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help