From: Paul Mackerras <paulus@samba.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: Version of dirdiff to display diffs between git trees
Date: Sat, 7 May 2005 10:01:18 +1000 [thread overview]
Message-ID: <17020.1358.415173.230113@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0505060916320.2233@ppc970.osdl.org>
Linus Torvalds writes:
> If you use git-pull-script, it does this for you (except it calls it
OK, cool
> ORIG_HEAD), and you can just do
>
> git-diff-tree -p ORIG_HEAD HEAD
>
> to see the changes. In fact git-pull-script will do that for you, and
> output the diffstat of it.
Yes, girdiff with two trees is mostly equivalent to git-diff-tree,
except that I find the girdiff/dirdiff display much easier to nagivate
and parse than a patch viewed in an xterm with less. (I say "mostly
equivalent" because if neither tree is the ancestor of the other,
girdiff looks at the common ancestor to get an idea of which tree has
the more recent version of each file that differs, and colors that one
green and the other red, which is extra information that git-diff-tree
doesn't give you.)
Similarly, girdiff with a tree and "." is equivalent to
git-diff-cache.
Girdiff also has the new dirdiff features of being able to expand the
displayed context for a hunk, to move changed lines up and down within
a hunk (provided the movement doesn't change the meaning of the diff),
and to split context lines into identical -/+ lines (which, together
with being able to move -/+ lines makes it possible to rearrange a
diff to make it more understandable).
If the working directory is one of the trees being diffed, you can
select parts of the diff for a file to be applied to the working
directory file. (You can't apply changes to a git tree, of course,
because it's immutable.) You can also select parts of the diff for a
file and generate a patch embodying just the selected changes.
Next I want to do a commit viewer with the ability to display the
differences between arbitrary points in the commit tree using girdiff.
Paul.
prev parent reply other threads:[~2005-05-06 23:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 13:18 Version of dirdiff to display diffs between git trees Paul Mackerras
2005-05-06 16:19 ` Linus Torvalds
2005-05-06 18:53 ` Krzysztof Halasa
2005-05-06 19:07 ` Linus Torvalds
2005-05-07 0:01 ` Paul Mackerras [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=17020.1358.415173.230113@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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