Re: [PATCH] show-branch: make --topo-order noop and default.

A Large Angry SCM [off-list ref] writes:

Junio C Hamano wrote:

quoted

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.

Junio C Hamano wrote:

A Large Angry SCM [off-list ref] writes:

quoted

Junio C Hamano wrote:

quoted

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?