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

Re: [PATCH] Fix git rev-list --reverse --max-count=N

From
Sverre Rabbelier <srabbelier@gmail.com>
Date
Jan 27, 2010, 22:17 UTC
Message-ID
<fabb9a1e1001271417w1c26fffdy379f8b845e4098b1@mail.gmail.com>
In-Reply-To
<201001272309.26054.j6t@kdbg.org>
Heya,
Show 18 quoted lines
> So when you have this history (A is oldest, D is newest):
>
>   A--B--C--D
>
> and you say
>
>   git log --max-count=2 --reverse D
>
> then you want
>
>   A
>   B
>
> but I want
>
>   C
>   D
>
And the current behavior is

B A

Isn't it? I agree btw, that C D is the 'correct' result.
-- 
Cheers,

Sverre Rabbelier
Previous: Johannes SixtNext: Michael Spang
Message 3 of 6 in “Fix git rev-list --reverse --max-count=N”
  1. Fix git rev-list --reverse --max-count=NMichael Spang, Jan 27, 2010
  2. Johannes SixtJan 27, 2010
  3. Sverre RabbelierJan 27, 2010
  4. Michael SpangJan 27, 2010
  5. Junio C HamanoJan 27, 2010
  6. Michael SpangJan 27, 2010

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.