git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@uchicago.edu>
To: Jerome Lovy <t2a2e9z8ncbs9qg@brefemail.com>
Cc: git@vger.kernel.org
Subject: Re: Puzzled by gitk patch representation for merge commits
Date: Fri, 4 Jul 2008 12:51:22 -0500 (CDT)	[thread overview]
Message-ID: <Pine.GSO.4.62.0807041240110.19792@harper.uchicago.edu> (raw)
In-Reply-To: <g4kpmu$9ga$1@ger.gmane.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN, Size: 1026 bytes --]

Hi Jérôme,

Jerome Lovy wrote:

> I don't understand the graphical scheme that gitk uses when displaying
> patches for merge commits. I would like to be able to explain this to the
> people I'm trying to evangelize to git, because they are also puzzled when
> they try to check with gitk what a merge has done to a given file.
> 
> I can see that at least three graphical hints seem to be involved:
> - font: regular/bold
> - color: red/blue
> (maybe there are more colors when the commit has more than two parents?)
> - column for displaying the '+' or '-'

All of the information is there in the text; the color and font are just
supposed to make it easier to see.  As for the diff text itself, I
didn't remember what it meant myself, so I looked it up.

It seems the diff format shown is that produced by 'git-diff --cc',
which makes a "compact combined diff".  It only shows conflicting
changes.  Each column on the left represents the changes from a
different parent.

Hope that helps,
Jonathan

      reply	other threads:[~2008-07-04 17:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-04  9:14 Puzzled by gitk patch representation for merge commits Jerome Lovy
2008-07-04 17:51 ` Jonathan Nieder [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=Pine.GSO.4.62.0807041240110.19792@harper.uchicago.edu \
    --to=jrnieder@uchicago.edu \
    --cc=git@vger.kernel.org \
    --cc=t2a2e9z8ncbs9qg@brefemail.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).