From: Teemu Likonen <tlikonen@iki.fi>
To: Junio C Hamano <gitster@pobox.com>
Cc: Adam Simpkins <adam@adamsimpkins.net>, git@vger.kernel.org
Subject: Re: log --graph --first-parent weirdness
Date: Wed, 4 Jun 2008 20:38:20 +0300 [thread overview]
Message-ID: <20080604173820.GA3038@mithlond.arda.local> (raw)
In-Reply-To: <7vmym1xgy4.fsf@gitster.siamese.dyndns.org>
Junio C Hamano wrote (2008-06-04 10:12 -0700):
> Teemu Likonen <tlikonen@iki.fi> writes:
>
> > The output of "git log --graph --first-parent" seems weird.
>
> Heh, --first-parent means "I'll view everything as a single strand of
> pearls". Who in the right mind would use --graph at the same time to
> begin with ;-)?
Exactly :) I have an alias "lg = log --graph" and I almost always use
that instead of the normal log. Then I accidentally noticed that my "git
lg" doesn't quite fit with --first-parent.
> We could turn --graph automatically off if --first-parent is given,
> but I tend to agree with you that the right behaviour is to show the
> same "everything prefixed with '| ', wasting two columns without good
> reason" output as you would see on a true linear history.
To me it's perfectly fine to turn off --graph when used with
--first-parent, but yes, generally users might expect to see a line of
M's, *'s and |'s there. At least it would clearly show which commits are
merges and which are not.
next prev parent reply other threads:[~2008-06-04 17:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 15:00 log --graph --first-parent weirdness Teemu Likonen
2008-06-04 15:08 ` Teemu Likonen
2008-06-04 17:12 ` Junio C Hamano
2008-06-04 17:38 ` Teemu Likonen [this message]
2008-06-04 18:04 ` Adam Simpkins
2008-06-05 8:56 ` [PATCH] graph API: fix "git log --graph --first-parent" Adam Simpkins
2008-06-04 18:05 ` log --graph --first-parent weirdness Junio C Hamano
2008-06-05 1:37 ` Ping Yin
2008-06-05 9:28 ` Adam Simpkins
2008-06-05 9:50 ` Teemu Likonen
2008-06-05 18:31 ` Junio C Hamano
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=20080604173820.GA3038@mithlond.arda.local \
--to=tlikonen@iki.fi \
--cc=adam@adamsimpkins.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).