From: Adam Simpkins <adam@adamsimpkins.net>
To: git@vger.kernel.org
Subject: Re: [PATCH 2/2] graph API: don't print branch lines for uninteresting merge parents
Date: Sat, 24 May 2008 15:21:01 -0700 [thread overview]
Message-ID: <20080524222101.GA6795@adamsimpkins.net> (raw)
In-Reply-To: <1211595851-11992-3-git-send-email-adam@adamsimpkins.net>
On Fri, May 23, 2008 at 07:24:11PM -0700, Adam Simpkins wrote:
> Previously, the graphing code printed lines coming out of a merge commit
> for all of its parents, even if some of them were uninteresting. Now it
> only prints lines for interesting commits.
>
> For example, for a merge commit where only the first parent is
> interesting, the code now prints:
>
> * merge commit
> * interesting child
>
> instead of:
>
> M merge commit
> |\
> * interesting child
Whoops. I forgot:
Signed-off-by: Adam Simpkins <adam@adamsimpkins.net>
--
Adam Simpkins
adam@adamsimpkins.net
prev parent reply other threads:[~2008-05-24 22:22 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
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 ` Adam Simpkins [this message]
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=20080524222101.GA6795@adamsimpkins.net \
--to=adam@adamsimpkins.net \
--cc=git@vger.kernel.org \
/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).