From: "Reece Dunn" <msclrhd@googlemail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Adam Simpkins" <adam@adamsimpkins.net>, git@vger.kernel.org
Subject: Re: bug in "git log --graph" at the tail end?
Date: Fri, 23 May 2008 22:02:10 +0100 [thread overview]
Message-ID: <3f4fd2640805231402n72aaed52l7a163168e9258f25@mail.gmail.com> (raw)
In-Reply-To: <7vve14rbu7.fsf@gitster.siamese.dyndns.org>
2008/5/23 Junio C Hamano <gitster@pobox.com>:
> It appears that "log --graph" output has a bug at its tail end.
>
> $ git log --pretty=oneline --abbrev-commit --graph 9d88058^..1af8bca
> M 1af8bca... Merge branch 'maint'
> |\
> | M 008442f... Merge branch 'maint-1.5.4' into maint
> | |\
> | * e77b0b5... git-am: fix typo in usage message
> | * 74190d2... doc/git-daemon: s/uploadarchive/uploadarch/
Shouldn't this be:
> | M 008442f... Merge branch 'maint-1.5.4' into maint
> | |\
> | | * e77b0b5... git-am: fix typo in usage message
> | | * 74190d2... doc/git-daemon: s/uploadarchive/uploadarch/
as well?
> This is purely cosmetic, but because --graph is only about the cosmetics,
> we may want to do something about it.
>
> Thoughts?
It is also consistent and makes the output easier to scan, so +1.
- Reece
next prev parent reply other threads:[~2008-05-23 21:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 20:42 bug in "git log --graph" at the tail end? Junio C Hamano
2008-05-23 21:02 ` Reece Dunn [this message]
2008-05-24 1:05 ` Adam Simpkins
2008-05-24 1:39 ` Junio C Hamano
2008-05-24 2:24 ` [PATCH 0/2] fix "log --graph" issues with uninteresting parents Adam Simpkins
2008-05-24 2:24 ` [PATCH 1/2] graph API: fix graph mis-alignment after uninteresting commits Adam Simpkins
2008-05-24 2:24 ` [PATCH 2/2] graph API: don't print branch lines for uninteresting merge parents Adam Simpkins
2008-05-24 18:25 ` Teemu Likonen
2008-05-24 20:52 ` [PATCH 0/1] graph API: always print 'M' for merge commits Adam Simpkins
2008-05-24 20:52 ` [PATCH 1/1] " Adam Simpkins
2008-05-24 22:21 ` Adam Simpkins
2008-05-25 1:28 ` [PATCH 0/1] " Junio C Hamano
2008-05-25 6:29 ` Teemu Likonen
2008-05-25 6:49 ` Adam Simpkins
2008-05-24 22:21 ` [PATCH 2/2] graph API: don't print branch lines for uninteresting merge parents Adam Simpkins
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=3f4fd2640805231402n72aaed52l7a163168e9258f25@mail.gmail.com \
--to=msclrhd@googlemail.com \
--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).