{"thread":{"id":"16335","subject":"reflog delete results in reflog show strangeness?","startedAt":"2008-11-14T22:33:10Z","lastAt":"2008-11-14T22:44:46Z","messageCount":2,"participants":["Bob Hiestand"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"95834","messageId":"cc29171c0811141433t43d27c5gb57ca11d2ddb67cb@mail.gmail.com","threadId":"16335","inReplyTo":null,"subject":"reflog delete results in reflog show strangeness?","fromName":"Bob Hiestand","fromEmail":"bob.hiestand@gmail.com","sentAt":"2008-11-14T22:33:10Z","receivedAt":"2008-11-14T22:33:10Z","isPatch":false,"sender":{"key":"bob.hiestand@gmail.com","avatar":null},"body":"I see a possible bug in the output of 'git reflog show' after using\n'git reflog delete'.  Simple example:\n\n$ git init\n$ git commit --allow-empty -m 'root'\n$ git commit --allow-empty -m 'good'\n$ git commit --allow-empty -m 'bad'\n$ git reflog\n996ca67... HEAD@{0}: commit: bad\ne431a20... HEAD@{1}: commit: good\n992dd88... HEAD@{2}: commit (initial): root\n\n$ git reset HEAD^\n$ git reflog\ne431a20... HEAD@{0}: HEAD^: updating HEAD\n996ca67... HEAD@{1}: commit: bad\ne431a20... HEAD@{2}: commit: good\n992dd88... HEAD@{3}: commit (initial): root\n\n$ git reflog delete HEAD@{1}\n$ git reflog\ne431a20... HEAD@{0}: HEAD^: updating HEAD\n996ca67... HEAD@{1}: commit: good\n992dd88... HEAD@{2}: commit (initial): root\n\nIn this listing, please note that, after the delete, the commit SHA\nshown as HEAD@{1} is that of the deleted reference (the bad commit)\nand does not match the reflog message, which has the expected value.\n\nThank you,\n\nbob\n"},{"id":"95835","messageId":"cc29171c0811141444t30a35c65se1319a63a5443354@mail.gmail.com","threadId":"16335","inReplyTo":"cc29171c0811141433t43d27c5gb57ca11d2ddb67cb@mail.gmail.com","subject":"Re: reflog delete results in reflog show strangeness?","fromName":"Bob Hiestand","fromEmail":"bob.hiestand@gmail.com","sentAt":"2008-11-14T22:44:46Z","receivedAt":"2008-11-14T22:44:46Z","isPatch":false,"sender":{"key":"bob.hiestand@gmail.com","avatar":null},"body":"On Fri, Nov 14, 2008 at 4:33 PM, Bob Hiestand <bob.hiestand@gmail.com> wrote:\n> I see a possible bug in the output of 'git reflog show' after using\n> 'git reflog delete'.  Simple example:\n>\n> $ git init\n> $ git commit --allow-empty -m 'root'\n> $ git commit --allow-empty -m 'good'\n> $ git commit --allow-empty -m 'bad'\n> $ git reflog\n> 996ca67... HEAD@{0}: commit: bad\n> e431a20... HEAD@{1}: commit: good\n> 992dd88... HEAD@{2}: commit (initial): root\n>\n> $ git reset HEAD^\n> $ git reflog\n> e431a20... HEAD@{0}: HEAD^: updating HEAD\n> 996ca67... HEAD@{1}: commit: bad\n> e431a20... HEAD@{2}: commit: good\n> 992dd88... HEAD@{3}: commit (initial): root\n>\n> $ git reflog delete HEAD@{1}\n> $ git reflog\n> e431a20... HEAD@{0}: HEAD^: updating HEAD\n> 996ca67... HEAD@{1}: commit: good\n> 992dd88... HEAD@{2}: commit (initial): root\n>\n> In this listing, please note that, after the delete, the commit SHA\n> shown as HEAD@{1} is that of the deleted reference (the bad commit)\n> and does not match the reflog message, which has the expected value.\n\nSorry, forgot to add this:\n\n$ git describe\nv1.6.0.4-969-g58a38d0\n"}]}