From: "Jan Krüger" <jk@jk.gs>
To: David Roundy <roundyd@physics.oregonstate.edu>
Cc: git@vger.kernel.org
Subject: Re: confusion with git diff-tree output
Date: Wed, 21 Oct 2009 19:51:03 +0200 [thread overview]
Message-ID: <20091021195103.01cef9c4@perceptron> (raw)
In-Reply-To: <117f2cc80910211043q3a92a7b6o15464cc049ee33dc@mail.gmail.com>
> David Roundy <roundyd@physics.oregonstate.edu> wrote:
> I've been struggling with trying to figure out how to make diff-tree
> output the actual files changed. Below is the output when I run
> diff-tree on a given commit. It reports that the directory is
> modified, rather than that a single file within that directory is
> modified.
Tree objects are recursively nested, i.e.
> 66b67ea1763799c0b2ac01f6803177ca870f6544 M Iolaus
is a reference to another tree object... and since a file in that
subtree changed, a new tree object that contains a different file
record is now referenced as "Iolaus".
By default git diff-tree doesn't recurse, but you can use -r for that.
Which is documented, I might add. ;)
Jan
next prev parent reply other threads:[~2009-10-21 17:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 17:43 confusion with git diff-tree output David Roundy
2009-10-21 17:51 ` Jan Krüger [this message]
2009-10-21 22:23 ` David Roundy
2009-10-21 22:42 ` Jan Krüger
2009-10-23 0:54 ` Jeff King
2009-10-24 6:36 ` Junio C Hamano
2009-10-24 9:51 ` Jeff King
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=20091021195103.01cef9c4@perceptron \
--to=jk@jk.gs \
--cc=git@vger.kernel.org \
--cc=roundyd@physics.oregonstate.edu \
/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).