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

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

From
MSMichael Spang <spang@google.com>
Date
Jan 27, 2010, 22:51 UTC
Message-ID
<abef960f1001271451n5ed454aaye1591ea35729b53f@mail.gmail.com>
In-Reply-To
<7vsk9rnpxo.fsf@alter.siamese.dyndns.org>
On Wed, Jan 27, 2010 at 5:28 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 9 quoted lines
> Johannes Sixt <j6t@kdbg.org> writes:
>
> The interaction between --max-count and --reverse was designed a long time
> ago to support "I want to review the recent N commits in order to make
> sure that they are natural and logical progression".  So an unconditional
> change of semantics to break that expectation this late in the game will
> never be acceptable, and giving title to such a patch with a word "Fix"
> won't fly well (it simply _breaks_ behaviour users have long learned to
> expect).

You have my apology for calling it a fix. I just don't have the same visibility into what undocumented behavior users depend on that you do, and so I thought it actually was one.

The patch can die here. I understand the current behavior now, and I don't have a strong need for the behavior I expected (piping to head works fine).

Michael
Previous: Junio C Hamano
Message 6 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.