git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: confusion with git diff-tree output

From
David Roundy <roundyd@physics.oregonstate.edu>
Date
Oct 21, 2009, 22:23 UTC
Message-ID
<117f2cc80910211523m5c1399aej594398fb6597e5de@mail.gmail.com>
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:
Show 10 quoted lines
> 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. ;)
Previous: Jan KrügerNext: Jan Krüger
Message 3 of 7 in “confusion with git diff-tree output”
  1. David RoundyOct 21, 2009
  2. Jan KrügerOct 21, 2009
  3. David RoundyOct 21, 2009
  4. Jan KrügerOct 21, 2009
  5. Jeff KingOct 23, 2009
  6. Junio C HamanoOct 24, 2009
  7. Jeff KingOct 24, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.