From: Linus Torvalds <torvalds@linux-foundation.org>
To: hanwen@xs4all.nl
Cc: git@vger.kernel.org
Subject: Re: git-log -p --raw broken?
Date: Tue, 6 Nov 2007 15:10:59 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.0.999.0711061508490.15101@woody.linux-foundation.org> (raw)
In-Reply-To: <f329bf540711061448iab9d4a9q37e13b846dbc5ff1@mail.gmail.com>
On Tue, 6 Nov 2007, Han-Wen Nienhuys wrote:
>
> The manual page suggests that I should be able to do
>
> git log -p --raw COMMIT-RANGE
>
> however, when I try that, I get always get the same style output,
> which is the (to me: useless) human readable output.
>
> Am I missing something?
No, you're not *missing* anything. You have something *too much*.
Please remove the "-p" if you don't want a patch.
This works:
git log --raw COMMIT-RANGE
(actually, most of the time you'd want to use "-r" too when you get raw
output, but git log enables that by default)
Linus
prev parent reply other threads:[~2007-11-06 23:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 22:48 git-log -p --raw broken? Han-Wen Nienhuys
2007-11-06 23:03 ` Han-Wen Nienhuys
2007-11-06 23:10 ` 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=alpine.LFD.0.999.0711061508490.15101@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=hanwen@xs4all.nl \
/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