git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>, Wincent Colaiuta <win@wincent.com>
Subject: Re: Side-by-side diff and patch visualization
Date: Wed, 19 Sep 2007 14:08:20 +0100	[thread overview]
Message-ID: <200709191408.21527.andyparkins@gmail.com> (raw)
In-Reply-To: <20070919120956.GA20715@coredump.intra.peff.net>

On Wednesday 2007 September 19, Jeff King wrote:

> Have you tried kompare?
>
>   git-diff HEAD~5 | kompare -

You can also throw in the "--unified" switch to see the whole file, rather 
than just the bits that have changed (if that's what you like).

 git-diff --unified=9999999 HEAD~5 | kompare -


Andy

-- 
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com

  parent reply	other threads:[~2007-09-19 13:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19 11:40 Side-by-side diff and patch visualization Wincent Colaiuta
2007-09-19 12:09 ` Jeff King
2007-09-19 12:36   ` Wincent Colaiuta
2007-09-19 13:08   ` Andy Parkins [this message]
2007-09-19 12:23 ` David Kastrup

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=200709191408.21527.andyparkins@gmail.com \
    --to=andyparkins@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=win@wincent.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).