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

Re: Git log range reverse bug

From
Derrick Stolee <stolee@gmail.com>
Date
May 16, 2018, 18:23 UTC
Message-ID
<d95c41a0-853a-e66e-da00-065f3ccf3c47@gmail.com>
In-Reply-To
<CAJeoX+5ZGFS0yhXwaESzx4kTHn9AOLVF5d2MBU-Sr8JeQRBSxA@mail.gmail.com>
Hi Mendi,
On 5/16/2018 2:19 PM, Mehdi Zeinali wrote:
Show 20 quoted lines
> 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

This command is asking for the commits reachable from HEAD but NOT reachable from 8e11b4a41ec21e47fb0bf8b76e1edba739f57a9b. To see 8e11b4a41ec21e47fb0bf8b76e1edba739f57a9b in the results, you would need to add "--boundary" to the command. That may still not show 8e11b4a41ec21e47fb0bf8b76e1edba739f57a9b as the first commit, as there may be multiple, earlier boundary commits.

Thanks, -Stolee

Previous: Mehdi ZeinaliNext: Johannes Sixt
Message 2 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.