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@xxxxxxxxxxxxxxx> Date: Mon Nov 3 19:01:53 2014 +0000 . . . $ git show Author: Some Other Name <SomeOtherName@xxxxxxxxxxxxxxx> 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
