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

Re: git rev-list ordering

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Nov 16, 2008, 21:16 UTC
Message-ID
<alpine.DEB.1.00.0811162215370.30769@pacific.mpi-cbg.de>
In-Reply-To
<alpine.LFD.2.00.0811152040570.2935@sys-0.hiltweb.site>
Hi,
On Sat, 15 Nov 2008, Ian Hilt wrote:
Show 9 quoted lines
> On Sat, 15 Nov 2008, Sverre Rabbelier wrote:
> > The --reverse is applied after the --max-count, so you are seeing the 
> > reverse of one commit ;). For comparison, have a look at:
> > 
> > $ git rev-list --reverse --max-count=2
> 
> Ah, I see.  So if you didn't want the sorting to take a long time for 
> many commits, you would limit the output to n commits, then sort the 
> output.  Is this the logic behind this design?

Yes. It is by design, since the guy who wrote the initial --reverse support cannot think of an interesting situation where you need to list the oldest n commits.

Ciao, Dscho

Previous: Ian HiltNext: Ian Hilt
Message 4 of 8 in “git rev-list ordering”
  1. Ian HiltNov 16, 2008
  2. Sverre RabbelierNov 16, 2008
  3. Ian HiltNov 16, 2008
  4. Johannes SchindelinNov 16, 2008
  5. Ian HiltNov 17, 2008
  6. Johannes SchindelinNov 17, 2008
  7. Pete HarlanNov 18, 2008
  8. Björn SteinbrinkNov 19, 2008

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.