{"thread":{"id":"10692","subject":"git-log -p --raw broken?","startedAt":"2007-11-06T22:48:43Z","lastAt":"2007-11-06T23:10:59Z","messageCount":3,"participants":["Han-Wen Nienhuys","Linus Torvalds"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"58606","messageId":"f329bf540711061448iab9d4a9q37e13b846dbc5ff1@mail.gmail.com","threadId":"10692","inReplyTo":null,"subject":"git-log -p --raw broken?","fromName":"Han-Wen Nienhuys","fromEmail":"hanwenn@gmail.com","sentAt":"2007-11-06T22:48:43Z","receivedAt":"2007-11-06T22:48:43Z","isPatch":false,"sender":{"key":"hanwenn@gmail.com","avatar":"https://gravatar.com/avatar/058832acb8d613baeb6ce9d21b009d9772424a309b9a521330423daef909a27a?d=mp&s=160"},"body":"Hi,\n\nI'm trying to get a list of\n\n  git diff-tree -t -r --raw COMMITTISH\n\nwhere COMMITTISH comes from git-rev-list, using a limited number of\nprocesses. The manual page suggests that I should be able to do\n\n git log -p --raw COMMIT-RANGE\n\nhowever, when I try that, I get always get the same style output,\nwhich is the (to me: useless) human readable output.\n\nAm I missing something?\n-- \nHan-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen\n"},{"id":"58607","messageId":"f329bf540711061503u4f5ba006p10d4e518812ae893@mail.gmail.com","threadId":"10692","inReplyTo":"f329bf540711061448iab9d4a9q37e13b846dbc5ff1@mail.gmail.com","subject":"Re: git-log -p --raw broken?","fromName":"Han-Wen Nienhuys","fromEmail":"hanwenn@gmail.com","sentAt":"2007-11-06T23:03:33Z","receivedAt":"2007-11-06T23:03:33Z","isPatch":false,"sender":{"key":"hanwenn@gmail.com","avatar":"https://gravatar.com/avatar/058832acb8d613baeb6ce9d21b009d9772424a309b9a521330423daef909a27a?d=mp&s=160"},"body":"2007/11/6, Han-Wen Nienhuys <hanwenn@gmail.com>:\n\n> I'm trying to get a list of\n>\n>   git diff-tree -t -r --raw COMMITTISH\n>\n> [..]\n\n> Am I missing something?\n\nI probably am, never mind this message.\n\\\n-- \nHan-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen\n"},{"id":"58608","messageId":"alpine.LFD.0.999.0711061508490.15101@woody.linux-foundation.org","threadId":"10692","inReplyTo":"f329bf540711061448iab9d4a9q37e13b846dbc5ff1@mail.gmail.com","subject":"Re: git-log -p --raw broken?","fromName":"Linus Torvalds","fromEmail":"torvalds@linux-foundation.org","sentAt":"2007-11-06T23:10:59Z","receivedAt":"2007-11-06T23:10:59Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Tue, 6 Nov 2007, Han-Wen Nienhuys wrote:\n>\n> The manual page suggests that I should be able to do\n> \n>  git log -p --raw COMMIT-RANGE\n> \n> however, when I try that, I get always get the same style output,\n> which is the (to me: useless) human readable output.\n> \n> Am I missing something?\n\nNo, you're not *missing* anything. You have something *too much*.\n\nPlease remove the \"-p\" if you don't want a patch.\n\nThis works:\n\n\tgit log --raw COMMIT-RANGE\n\n(actually, most of the time you'd want to use \"-r\" too when you get raw \noutput, but git log enables that by default)\n\n\t\t\tLinus\n"}]}