From: David Roundy <roundyd@physics.oregonstate.edu>
To: git@vger.kernel.org
Subject: Re: confusion with git diff-tree output
Date: Wed, 21 Oct 2009 18:23:08 -0400 [thread overview]
Message-ID: <117f2cc80910211523m5c1399aej594398fb6597e5de@mail.gmail.com> (raw)
In-Reply-To: <20091021195103.01cef9c4@perceptron>
You're right. I figured I must be overlooking something obvious, and
that was it. What surprised me was that -p implies -r, which is not
documented. Since the -p output was recursive, I incorrectly presumed
that this was the default.
David
On Wed, Oct 21, 2009 at 1:51 PM, Jan Krüger <jk@jk.gs> wrote:
> 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. ;)
next prev parent reply other threads:[~2009-10-21 22:23 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
2009-10-21 22:23 ` David Roundy [this message]
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=117f2cc80910211523m5c1399aej594398fb6597e5de@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).