From: "Sverre Rabbelier" <alturin@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Adam Simpkins" <adam@adamsimpkins.net>,
git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] log --graph: draw '>' and '<' with --left-right
Date: Thu, 22 May 2008 15:14:13 +0200 [thread overview]
Message-ID: <bd6139dc0805220614l2504ca0bk432d3101d853b28c@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0805221344360.30431@racer>
On Thu, May 22, 2008 at 2:47 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Sverre just notified me that the commit message is not brilliant. How
> about this:
>
> -- snip --
> When calling "git log --left-right <branch1>...<branch2>", a single "<" or
> ">" is shown in front of the commit line, to indicate which branch1 this
> commit comes from, branch1 or branch2.
>
> However, it is easy to miss in the output of "git log --graph ...", since
> the graph still has "*" for regular commits and "M" for merge commits. So
> imitate gitk, and show the "<" and ">" characters in the graph, too,
> instead of "*" (or "M").
> -- snap --
I admit that I didn't know how gitk does things, but yeah, this is a
lot more explanatory and makes sense :).
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2008-05-22 13:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 11:36 [PATCH] log --graph: draw '>' and '<' with --left-right Johannes Schindelin
2008-05-22 12:47 ` Johannes Schindelin
2008-05-22 13:14 ` Sverre Rabbelier [this message]
2008-05-25 5:27 ` Junio C Hamano
2008-05-25 6:43 ` Adam Simpkins
2008-05-25 7:07 ` [PATCH] log and rev-list: don't print extra prefixes already shown in the graph 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=bd6139dc0805220614l2504ca0bk432d3101d853b28c@mail.gmail.com \
--to=alturin@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=adam@adamsimpkins.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sverre@rabbelier.nl \
/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).