threads / discuss / 10692

git-log -p --raw broken?

Subject: git-log -p --raw broken?

## tl;dr

3 messages between Nov 6, 2007 and Nov 6, 2007.

replies: 2people: 2as markdown or json

Han-Wen Nienhuys· Nov 6, 2007, 22:48 UTC · lore

Hi,

I'm trying to get a list of

  git diff-tree -t -r --raw COMMITTISH

where COMMITTISH comes from git-rev-list, using a limited number of processes. 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?

-- 
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen

Han-Wen Nienhuys· Nov 6, 2007, 23:03 UTC · re: Han-Wen Nienhuys · lore

Re: git-log -p --raw broken?

2007/11/6, Han-Wen Nienhuys <hanwenn@gmail.com>:

Show 5 quoted lines

> I'm trying to get a list of
>
>   git diff-tree -t -r --raw COMMITTISH
>
> [..]

> Am I missing something?

I probably am, never mind this message. \

-- 
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen

Linus Torvalds· Nov 6, 2007, 23:10 UTC · re: Han-Wen Nienhuys · lore

Re: git-log -p --raw broken?

On Tue, 6 Nov 2007, Han-Wen Nienhuys wrote:

Show 9 quoted lines

>
> 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