Re: Git log range reverse bug

[Johannes Sixt]

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