From: Junio C Hamano <junkio@cox.net>
To: gitzilla@gmail.com
Cc: git@vger.kernel.org
Subject: Re: [PATCH] show-branch: make --topo-order noop and default.
Date: Thu, 12 Jan 2006 20:11:55 -0800 [thread overview]
Message-ID: <7vslrsg41g.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <43C70F69.7010103@gmail.com> (A. Large Angry's message of "Thu, 12 Jan 2006 18:24:41 -0800")
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.
next prev parent reply other threads:[~2006-01-13 4:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 0:05 [PATCH] show-branch: make --topo-order noop and default Junio C Hamano
2006-01-13 2:24 ` A Large Angry SCM
2006-01-13 4:11 ` Junio C Hamano [this message]
2006-01-13 5:28 ` A Large Angry SCM
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vslrsg41g.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=gitzilla@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).