From: A Large Angry SCM <gitzilla@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] show-branch: make --topo-order noop and default.
Date: Thu, 12 Jan 2006 18:24:41 -0800 [thread overview]
Message-ID: <43C70F69.7010103@gmail.com> (raw)
In-Reply-To: <7v4q4ajonx.fsf@assigned-by-dhcp.cox.net>
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.
next prev parent reply other threads:[~2006-01-13 2:24 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 [this message]
2006-01-13 4:11 ` Junio C Hamano
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=43C70F69.7010103@gmail.com \
--to=gitzilla@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.