git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "David Kågedal" <davidk@lysator.liu.se>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Output from git diff-tree (documentation)
Date: Mon, 27 Jul 2009 14:03:27 -0700	[thread overview]
Message-ID: <7vbpn5g7og.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <87hbwxaolw.fsf@krank.kagedal.org> ("David Kågedal"'s message of "Mon\, 27 Jul 2009 21\:54\:19 +0200")

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.

  reply	other threads:[~2009-07-27 21:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27 19:54 Output from git diff-tree (documentation) David Kågedal
2009-07-27 21:03 ` Junio C Hamano [this message]
     [not found]   ` <87vdld9694.fsf@krank.kagedal.org>
     [not found]     ` <87prbl8ay5.fsf_-_@krank.kagedal.org>
2009-07-28 20:34       ` [PATCH] Update the documentation of the raw diff output format Junio C Hamano
2009-07-29  6:11         ` David Kågedal
2009-07-29 17:20 ` Output from git diff David Kågedal
2009-07-29 17:29   ` Pat Notz
2009-07-29 18:26   ` Junio C Hamano
     [not found]     ` <87y6q6ehx8.fsf@krank.kagedal.org>
2009-07-30  8:06       ` Junio C Hamano

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=7vbpn5g7og.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=davidk@lysator.liu.se \
    --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).