From: A Large Angry SCM <gitzilla@gmail.com>
Date: Fri, 13 Jan 2006 05:28:21 GMT
Subject: Re: [PATCH] show-branch: make --topo-order noop and default.
Message-ID: <43C73A75.6020007@gmail.com>
In-Reply-To: <7vslrsg41g.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:
> A Large Angry SCM <gitzilla@gmail.com> writes:
> 
>>Junio C Hamano wrote:
>>>It really does not make sense not doing --topo-order.
>>I disagree. I do like to see the chronological commit history of some
>>repositories.
> 
> But the thing is if you do chronological order, you may not see
> enough commits without --more=, because show-branches stops at
> the first common commit.  Try it yourself in a repository with
> merges on topic branches of different vintage, with and without
> the option, to see where output stops.

Interesting, I don't think I've ever looked far enough to triggered the 
stop condition in my repositories of interest before.

How about making topo-order the default but having an option for 
chronological order?