From: Ian Hilt <ian.hilt@gmx.com>
Date: Sun, 16 Nov 2008 01:44:18 GMT
Subject: Re: git rev-list ordering
Message-ID: <alpine.LFD.2.00.0811152040570.2935@sys-0.hiltweb.site>
In-Reply-To: <bd6139dc0811151727k605a3575hf409fed32a3a4baf@mail.gmail.com>

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?