git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git log range reverse bug

From
Johannes Sixt <j6t@kdbg.org>
Date
May 16, 2018, 21:02 UTC
Message-ID
<29bf5b72-8156-5098-ee56-b7c4fea1343c@kdbg.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
Previous: Derrick Stolee
Message 3 of 3 in “Git log range reverse bug”
  1. Mehdi ZeinaliMay 16, 2018
  2. Derrick StoleeMay 16, 2018
  3. Johannes SixtMay 16, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.