From: Jon Loeliger <jdl@freescale.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
pasky@suse.cz, git@vger.kernel.org
Subject: Re: [PATCH 2/2] sort_in_topological_order(): avoid setting a commit flag
Date: Wed, 23 Jul 2008 10:39:55 -0500 [thread overview]
Message-ID: <488750CB.1040400@freescale.com> (raw)
In-Reply-To: <7v7ibdifbp.fsf@gitster.siamese.dyndns.org>
Junio C Hamano wrote:
>
> Do people still actively use show-branch as a G/CUI, especially after that
> "log --graph" thing was introduced?
At the risk of sounding Old School, yes.
While the "log --graph" thing is Really Slick, it has
grumbly-factors, IMO. First, I have to set up an alias
all the time, as "git log --graph --pretty=oneline" is
grumpy typing. Second, I always have to widen my screen
to accommodate reasonable looking output or colrm it.
(Having it self-colrm to window-width would be nice.)
(Sure, --abbrev-commit too, but see "First," above. :-))
Finally, I frequently like seeing a self-limited history
when all the branches reach their common ancestor.
HTH,
jdl
next prev parent reply other threads:[~2008-07-23 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 0:50 [PATCH 1/2] Add test to show that show-branch misses out the 8th column Johannes Schindelin
2008-07-23 0:51 ` [PATCH 2/2] sort_in_topological_order(): avoid setting a commit flag Johannes Schindelin
2008-07-23 1:01 ` Junio C Hamano
2008-07-23 15:39 ` Jon Loeliger [this message]
2008-07-23 21:49 ` Petr Baudis
2008-07-23 22:07 ` Junio C Hamano
2008-07-23 19:02 ` Junio C Hamano
2008-07-23 19:33 ` Johannes Schindelin
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=488750CB.1040400@freescale.com \
--to=jdl@freescale.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pasky@suse.cz \
/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.