* Git log range reverse bug
@ 2018-05-16 18:19 Mehdi Zeinali
2018-05-16 18:23 ` Derrick Stolee
2018-05-16 21:02 ` Johannes Sixt
0 siblings, 2 replies; 3+ messages in thread
From: Mehdi Zeinali @ 2018-05-16 18:19 UTC (permalink / raw)
To: git
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Git log range reverse bug
2018-05-16 18:19 Git log range reverse bug Mehdi Zeinali
@ 2018-05-16 18:23 ` Derrick Stolee
2018-05-16 21:02 ` Johannes Sixt
1 sibling, 0 replies; 3+ messages in thread
From: Derrick Stolee @ 2018-05-16 18:23 UTC (permalink / raw)
To: Mehdi Zeinali, git
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Git log range reverse bug
2018-05-16 18:19 Git log range reverse bug Mehdi Zeinali
2018-05-16 18:23 ` Derrick Stolee
@ 2018-05-16 21:02 ` Johannes Sixt
1 sibling, 0 replies; 3+ messages in thread
From: Johannes Sixt @ 2018-05-16 21:02 UTC (permalink / raw)
To: Mehdi Zeinali; +Cc: git
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-05-16 21:02 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-05-16 18:19 Git log range reverse bug Mehdi Zeinali
2018-05-16 18:23 ` Derrick Stolee
2018-05-16 21:02 ` Johannes Sixt
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).