From: "André Goddard Rosa" <andre.goddard@gmail.com>
To: "Robin Rosenberg" <robin.rosenberg.lists@dewire.com>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Using kdiff3 to compare two different revisions of a folder
Date: Wed, 13 Feb 2008 22:36:34 -0200 [thread overview]
Message-ID: <b8bf37780802131636q698ebb21kc415328c04d8425d@mail.gmail.com> (raw)
In-Reply-To: <200802132338.18449.robin.rosenberg.lists@dewire.com>
> > Is there a better way to do this kind of comparison?
>
> Yes.
> git diff <whatever options> | kompare -
>
Thanks, Robin! It works too.
--
[]s,
André Goddard
next prev parent reply other threads:[~2008-02-14 0:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 1:44 Using kdiff3 to compare two different revisions of a folder André Goddard Rosa
2008-02-13 17:44 ` Brian Downing
2008-02-14 0:37 ` André Goddard Rosa
2008-02-13 22:38 ` Robin Rosenberg
2008-02-14 0:36 ` André Goddard Rosa [this message]
2008-02-17 10:51 ` Jan Hudec
2008-02-17 11:35 ` André Goddard Rosa
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=b8bf37780802131636q698ebb21kc415328c04d8425d@mail.gmail.com \
--to=andre.goddard@gmail.com \
--cc=git@vger.kernel.org \
--cc=robin.rosenberg.lists@dewire.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).