{"thread":{"id":"48506","subject":"Git log range reverse bug","startedAt":"2018-05-16T18:19:24Z","lastAt":"2018-05-16T21:02:43Z","messageCount":3,"participants":["Mehdi Zeinali","Derrick Stolee","Johannes Sixt"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"347806","messageId":"CAJeoX+5ZGFS0yhXwaESzx4kTHn9AOLVF5d2MBU-Sr8JeQRBSxA@mail.gmail.com","threadId":"48506","inReplyTo":null,"subject":"Git log range reverse bug","fromName":"Mehdi Zeinali","fromEmail":"zeinali8@gmail.com","sentAt":"2018-05-16T18:19:17Z","receivedAt":"2018-05-16T18:19:24Z","isPatch":false,"sender":{"key":"zeinali8@gmail.com","avatar":null},"body":"Git Version: Version: 2.14.2\n\nWhen reversing a range in git log, it does not start from the expected commit:\n\n$ git show 8e11b4a41ec21e47fb0bf8b76e1edba739f57a9b\ncommit 8e11b4a41ec21e47fb0bf8b76e1edba739f57a9b\nAuthor: Some Name <SomeName@SomeAddress.com>\nDate:   Mon Nov 3 19:01:53 2014 +0000\n.\n.\n.\n\n$ git show\nAuthor: Some Other Name <SomeOtherName@SomeAddress.com>\nDate:   Wed May 16 16:49:10 2018 +0000\n.\n.\n.\n\n$ git log --reverse 8e11b4a41ec21e47fb0bf8b76e1edba739f57a9b..HEAD\ncommit b4cfdb39f75070f143cdc2c4fbb98f4c6ee94260\nAuthor: Another Name <AnotherName@SomeAddress.com>\nDate:   Mon Apr 29 22:16:32 2013 +0000\nSome Commit message\n\ncommit 6e6d5cd2a07985ae647fc19e7404ce1edf908949\nAuthor: Yet Another Name <YetAnotherName@SomeAddress.com>\nDate:   Mon Apr 29 22:35:00 2013 +0000\nSome other Commit message\n\n.\n.\n.\n\nAs you can see, the first commit is way off of the provided hash\nMehdi\n"},{"id":"347807","messageId":"d95c41a0-853a-e66e-da00-065f3ccf3c47@gmail.com","threadId":"48506","inReplyTo":"CAJeoX+5ZGFS0yhXwaESzx4kTHn9AOLVF5d2MBU-Sr8JeQRBSxA@mail.gmail.com","subject":"Re: Git log range reverse bug","fromName":"Derrick Stolee","fromEmail":"stolee@gmail.com","sentAt":"2018-05-16T18:23:02Z","receivedAt":"2018-05-16T18:23:08Z","isPatch":false,"sender":{"key":"stolee@gmail.com","avatar":"https://avatars.githubusercontent.com/u/570044?v=4"},"body":"Hi Mendi,\n\nOn 5/16/2018 2:19 PM, Mehdi Zeinali wrote:\n> Git Version: Version: 2.14.2\n>\n> When reversing a range in git log, it does not start from the expected commit:\n>\n> $ git show 8e11b4a41ec21e47fb0bf8b76e1edba739f57a9b\n> commit 8e11b4a41ec21e47fb0bf8b76e1edba739f57a9b\n> Author: Some Name <SomeName@SomeAddress.com>\n> Date:   Mon Nov 3 19:01:53 2014 +0000\n> .\n> .\n> .\n>\n> $ git show\n> Author: Some Other Name <SomeOtherName@SomeAddress.com>\n> Date:   Wed May 16 16:49:10 2018 +0000\n> .\n> .\n> .\n>\n> $ git log --reverse 8e11b4a41ec21e47fb0bf8b76e1edba739f57a9b..HEAD\n\nThis command is asking for the commits reachable from HEAD but NOT \nreachable from 8e11b4a41ec21e47fb0bf8b76e1edba739f57a9b. To see \n8e11b4a41ec21e47fb0bf8b76e1edba739f57a9b in the results, you would need \nto add \"--boundary\" to the command. That may still not show \n8e11b4a41ec21e47fb0bf8b76e1edba739f57a9b as the first commit, as there \nmay be multiple, earlier boundary commits.\n\nThanks,\n-Stolee\n"},{"id":"347824","messageId":"29bf5b72-8156-5098-ee56-b7c4fea1343c@kdbg.org","threadId":"48506","inReplyTo":"CAJeoX+5ZGFS0yhXwaESzx4kTHn9AOLVF5d2MBU-Sr8JeQRBSxA@mail.gmail.com","subject":"Re: Git log range reverse bug","fromName":"Johannes Sixt","fromEmail":"j6t@kdbg.org","sentAt":"2018-05-16T21:02:37Z","receivedAt":"2018-05-16T21:02:43Z","isPatch":false,"sender":{"key":"j6t@kdbg.org","avatar":"https://avatars.githubusercontent.com/u/14810926?v=4"},"body":"Am 16.05.2018 um 20:19 schrieb Mehdi Zeinali:\n> Git Version: Version: 2.14.2\n> \n> When reversing a range in git log, it does not start from the expected commit:\n\n--reverse does not change the meaning A..B to B..A or something. For a \nparticular A..B specification, the set of commits selected when \n--reverse is given remains the same. Only the order in which they are \nlisted is reversed.\n\n-- Hannes\n"}]}