From: Linus Torvalds <torvalds@osdl.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Tweak git-diff-tree -v output further.
Date: Fri, 6 May 2005 14:54:24 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0505061451530.2233@ppc970.osdl.org> (raw)
In-Reply-To: <7vd5s4cfzq.fsf@assigned-by-dhcp.cox.net>
On Fri, 6 May 2005, Junio C Hamano wrote:
>
> This adds the full header information to git-diff-tree -v output
> in addition to the log message it already produces.
I don't actually like the git internal commit format, it's not very
readable. It's designed to be nicely readable by machines, not humans.
If you want machine-readable output, you shouldn't use "-v" (or probably
-p either) anyway, you'd be better off with the raw file changes.
> Maybe we want to stop indenting so that it matches what
> git-export produces better.
Again, it's indented so that it's human-readable, and I was planning on
adding _some_ human-readable output from the headers (author and a
human-readable date or something).
Linus
prev parent reply other threads:[~2005-05-06 21:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 19:27 [PATCH] Tweak git-diff-tree -v output further Junio C Hamano
2005-05-06 21:54 ` Linus Torvalds [this message]
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=Pine.LNX.4.58.0505061451530.2233@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).