From: David Roundy <roundyd@physics.oregonstate.edu>
To: git@vger.kernel.org
Subject: confusion with git diff-tree output
Date: Wed, 21 Oct 2009 13:43:40 -0400 [thread overview]
Message-ID: <117f2cc80910211043q3a92a7b6o15464cc049ee33dc@mail.gmail.com> (raw)
Hi all,
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. I can find out what *file* was modified by running
diff-tree -p --raw, which gives me output similar to what I expected
from a plain old diff-tree. Is there a flag that will make diff-tree
give this information?
As background, what I really want is --name-only, which rarely reports
the files modified, instead reporting the directories as modified, and
I've been struggling to figure out what is going on. The
documentation seems to imply that the --raw diff output will report
modified files, and I haven't found anything indicating when it would
report the directories containing the modified files instead.
Thanks!
David
$ git diff-tree fd99a198222c14cf42fee82087a13467ff4a8205
fd99a198222c14cf42fee82087a13467ff4a8205
:040000 040000 8cdb796ea801da99c34d8f60045d8eb08fbb0e41
66b67ea1763799c0b2ac01f6803177ca870f6544 M Iolaus
$ git diff-tree fd99a198222c14cf42fee82087a13467ff4a8205 -p --raw
fd99a198222c14cf42fee82087a13467ff4a8205
:100644 100644 dab4c531f3f69f08e5dc202ad8b6dfad9e8855fe
0e3f305e641a6440bb478765dfcd089e0420c155 M Iolaus/Lcs2.hs
diff --git a/Iolaus/Lcs2.hs b/Iolaus/Lcs2.hs
index dab4c53..0e3f305 100644
--- a/Iolaus/Lcs2.hs
+++ b/Iolaus/Lcs2.hs
(changes cut)
next reply other threads:[~2009-10-21 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 17:43 David Roundy [this message]
2009-10-21 17:51 ` confusion with git diff-tree output Jan Krüger
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=117f2cc80910211043q3a92a7b6o15464cc049ee33dc@mail.gmail.com \
--to=roundyd@physics.oregonstate.edu \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).