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

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

From
Junio C Hamano <junkio@cox.net>
Date
Jan 13, 2006, 04:11 UTC
Message-ID
<7vslrsg41g.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<43C70F69.7010103@gmail.com>
A Large Angry SCM <gitzilla@gmail.com> writes:
Show 5 quoted lines
> 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.

Previous: A Large Angry SCMNext: A Large Angry SCM
Message 3 of 4 in “show-branch: make --topo-order noop and default.”
  1. show-branch: make --topo-order noop and default.Junio C Hamano, Jan 12, 2006
  2. A Large Angry SCMJan 13, 2006
  3. Junio C HamanoJan 13, 2006
  4. A Large Angry SCMJan 13, 2006

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.