git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Git log range reverse bug

From
MZMehdi Zeinali <zeinali8@gmail.com>
Date
May 16, 2018, 18:19 UTC
Message-ID
<CAJeoX+5ZGFS0yhXwaESzx4kTHn9AOLVF5d2MBU-Sr8JeQRBSxA@mail.gmail.com>
Git Version: Version: 2.14.2
When reversing a range in git log, it does not start from the expected commit:
$ git show 8e11b4a41ec21e47fb0bf8b76e1edba739f57a9b
commit 8e11b4a41ec21e47fb0bf8b76e1edba739f57a9b
Author: Some Name <SomeName@SomeAddress.com>
Date:   Mon Nov 3 19:01:53 2014 +0000
.
.
.
$ git show
Author: Some Other Name <SomeOtherName@SomeAddress.com>
Date:   Wed May 16 16:49:10 2018 +0000
.
.
.
$ git log --reverse 8e11b4a41ec21e47fb0bf8b76e1edba739f57a9b..HEAD
commit b4cfdb39f75070f143cdc2c4fbb98f4c6ee94260
Author: Another Name <AnotherName@SomeAddress.com>
Date:   Mon Apr 29 22:16:32 2013 +0000
Some Commit message
commit 6e6d5cd2a07985ae647fc19e7404ce1edf908949
Author: Yet Another Name <YetAnotherName@SomeAddress.com>
Date:   Mon Apr 29 22:35:00 2013 +0000
Some other Commit message

. . .

As you can see, the first commit is way off of the provided hash Mehdi

Next: Derrick Stolee
Message 1 of 3 in “Git log range reverse bug”
  1. Mehdi ZeinaliMay 16, 2018
  2. Derrick StoleeMay 16, 2018
  3. Johannes SixtMay 16, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.