# Git log range reverse bug

3 messages from 2018-05-16 to 2018-05-16. Participants: Mehdi Zeinali, Derrick Stolee, Johannes Sixt.
Thread: https://gitlist.dev/t/48506

## Mehdi Zeinali, 2018-05-16 18:19

Subject: Git log range reverse bug
Message-ID: <CAJeoX+5ZGFS0yhXwaESzx4kTHn9AOLVF5d2MBU-Sr8JeQRBSxA@mail.gmail.com>
URL: https://gitlist.dev/e/CAJeoX%2B5ZGFS0yhXwaESzx4kTHn9AOLVF5d2MBU-Sr8JeQRBSxA%40mail.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

```

## Derrick Stolee, 2018-05-16 18:23

Subject: Re: Git log range reverse bug
Message-ID: <d95c41a0-853a-e66e-da00-065f3ccf3c47@gmail.com>
URL: https://gitlist.dev/e/d95c41a0-853a-e66e-da00-065f3ccf3c47%40gmail.com
In-Reply-To: <CAJeoX+5ZGFS0yhXwaESzx4kTHn9AOLVF5d2MBU-Sr8JeQRBSxA@mail.gmail.com>

```
Hi Mendi,

On 5/16/2018 2:19 PM, Mehdi Zeinali wrote:
> 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

```

## Johannes Sixt, 2018-05-16 21:02

Subject: Re: Git log range reverse bug
Message-ID: <29bf5b72-8156-5098-ee56-b7c4fea1343c@kdbg.org>
URL: https://gitlist.dev/e/29bf5b72-8156-5098-ee56-b7c4fea1343c%40kdbg.org
In-Reply-To: <CAJeoX+5ZGFS0yhXwaESzx4kTHn9AOLVF5d2MBU-Sr8JeQRBSxA@mail.gmail.com>

```
Am 16.05.2018 um 20:19 schrieb Mehdi Zeinali:
> Git Version: Version: 2.14.2
> 
> When reversing a range in git log, it does not start from the expected commit:

--reverse does not change the meaning A..B to B..A or something. For a 
particular A..B specification, the set of commits selected when 
--reverse is given remains the same. Only the order in which they are 
listed is reversed.

-- Hannes

```