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

Re: Output from git diff-tree (documentation)

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 27, 2009, 21:03 UTC
Message-ID
<7vbpn5g7og.fsf@alter.siamese.dyndns.org>
In-Reply-To
<87hbwxaolw.fsf@krank.kagedal.org>
David Kågedal <davidk@lysator.liu.se> writes:
> The "git diff-tree HEAD" command (with the default raw output) starts
> by printing a hash, which seems to be the hash for the commit (HEAD in
> this case).

That was because "git diff-tree" was the historical workhorse of "git log". The latter literally was "rev-list HEAD | git diff-tree --stdin".

Giving a commit on the command line and giving one from the stdin was made consistent. IOW, "rev-list HEAD | xargs -n1 git diff-tree" would give you a similar output.

Previous: David KågedalNext: David Kågedal
Message 2 of 8 in “Output from git diff-tree (documentation)”
  1. David KågedalJul 27, 2009
  2. Junio C HamanoJul 27, 2009
  3. Output from git diffDavid Kågedal, Jul 29, 2009
  4. Pat NotzJul 29, 2009
  5. Junio C HamanoJul 29, 2009
  6. Junio C HamanoJul 28, 2009
  7. David KågedalJul 29, 2009
  8. Junio C HamanoJul 30, 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.