Re: [BUG] git-rev-list: --topo-order --boundary and --max-count

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Mar 5, 2007, 17:05 UTC
Message-ID: <Pine.LNX.4.64.0703050901370.3998@woody.linux-foundation.org>
In-Reply-To: <7vlkicynwm.fsf@assigned-by-dhcp.cox.net>

On Mon, 5 Mar 2007, Junio C Hamano wrote:

> 
> I think the code that does --boundary when the list is limited
> with --max-count is not quite right, even without topo-order.

Yeah. Sadly, this is a really irritating bug, becuase it means that you cannot do

	gitk -50

to see some random collection of 50 recent commits.

(And yes, I've wanted to do that - I know the commit is fairly recent, so rather than write "gitk @{1.hour.ag}..", I'd rather just be lazy and say "gitk -100" to get a smaller slider bar and easier to find the recent ones).

I never cared enough to fix it, but it's a mis-feature. I agree that it's probably not entirely trivial to fix.

		Linus