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

Re: confusion with git diff-tree output

From
Jan Krüger <jk@jk.gs>
Date
Oct 21, 2009, 17:51 UTC
Message-ID
<20091021195103.01cef9c4@perceptron>
In-Reply-To
<117f2cc80910211043q3a92a7b6o15464cc049ee33dc@mail.gmail.com>
> David Roundy <roundyd@physics.oregonstate.edu> wrote:
Show 5 quoted lines
> 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
Previous: David RoundyNext: David Roundy
Message 2 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.