{"thread":{"id":"20250","subject":"Output from git diff-tree (documentation)","startedAt":"2009-07-27T19:54:19Z","lastAt":"2009-07-30T08:06:41Z","messageCount":8,"participants":["David Kågedal","Junio C Hamano","Pat Notz"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"118901","messageId":"87hbwxaolw.fsf@krank.kagedal.org","threadId":"20250","inReplyTo":null,"subject":"Output from git diff-tree (documentation)","fromName":"David Kågedal","fromEmail":"davidk@lysator.liu.se","sentAt":"2009-07-27T19:54:19Z","receivedAt":"2009-07-27T19:54:19Z","isPatch":false,"sender":{"key":"davidk@lysator.liu.se","avatar":"https://avatars.githubusercontent.com/u/60530?v=4"},"body":"The \"git diff-tree HEAD\" command (with the default raw output) starts\nby printing a hash, which seems to be the hash for the commit (HEAD in\nthis case).\n\nI can't find any description of this in the documentation for\ndiff-tree.\n\nThe \"output format\" sectionis the generic diff-format.txt that\ndescribes the format of the lines for the files that differ. Nothing\nwrong with that, but it doesn't explain the initial line of diff-tree.\n\nThe documentation of the --stdin flag mentions some initial output,\nbut that is not relevant in this case.\n\n-- \nDavid Kågedal\n"},{"id":"118903","messageId":"7vbpn5g7og.fsf@alter.siamese.dyndns.org","threadId":"20250","inReplyTo":"87hbwxaolw.fsf@krank.kagedal.org","subject":"Re: Output from git diff-tree (documentation)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-07-27T21:03:27Z","receivedAt":"2009-07-27T21:03:27Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"David Kågedal <davidk@lysator.liu.se> writes:\n\n> The \"git diff-tree HEAD\" command (with the default raw output) starts\n> by printing a hash, which seems to be the hash for the commit (HEAD in\n> this case).\n\nThat was because \"git diff-tree\" was the historical workhorse of \"git\nlog\".  The latter literally was \"rev-list HEAD | git diff-tree --stdin\".\n\nGiving a commit on the command line and giving one from the stdin was made\nconsistent.  IOW, \"rev-list HEAD | xargs -n1 git diff-tree\" would give you\na similar output.\n"},{"id":"118983","messageId":"7vhbww5yxb.fsf@alter.siamese.dyndns.org","threadId":"20250","inReplyTo":"87prbl8ay5.fsf_-_@krank.kagedal.org","subject":"Re: [PATCH] Update the documentation of the raw diff output format","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-07-28T20:34:56Z","receivedAt":"2009-07-28T20:34:56Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Looks reasonable; thanks.\n"},{"id":"119016","messageId":"873a8grpay.fsf@krank.kagedal.org","threadId":"20250","inReplyTo":"7vhbww5yxb.fsf@alter.siamese.dyndns.org","subject":"Re: [PATCH] Update the documentation of the raw diff output format","fromName":"David Kågedal","fromEmail":"davidk@lysator.liu.se","sentAt":"2009-07-29T06:11:49Z","receivedAt":"2009-07-29T06:11:49Z","isPatch":true,"sender":{"key":"davidk@lysator.liu.se","avatar":"https://avatars.githubusercontent.com/u/60530?v=4"},"body":"Junio C Hamano <gitster@pobox.com> writes:\n\n> Looks reasonable; thanks.\n\nGreat. But my patch mail doesn't seem to have reached the list, for\nsome reason. At least I can't find it in gmane.\n\n-- \nDavid Kågedal\n"},{"id":"119083","messageId":"873a8fflt2.fsf@krank.kagedal.org","threadId":"20250","inReplyTo":"87hbwxaolw.fsf@krank.kagedal.org","subject":"Output from git diff","fromName":"David Kågedal","fromEmail":"davidk@lysator.liu.se","sentAt":"2009-07-29T17:20:25Z","receivedAt":"2009-07-29T17:20:25Z","isPatch":false,"sender":{"key":"davidk@lysator.liu.se","avatar":"https://avatars.githubusercontent.com/u/60530?v=4"},"body":"Here is another diff output question. The updated documentation in\ndiff-format.txt still claims that the output from the diff commands\nhas this format:\n\n:100644 100644 bcd1234... 0123456... M file0\n\nThis is true for \"git diff --raw\", but diff-tree and friends print\nfull 40-char hashes.\n\nI can get diff-tree to use abbreviated hashes with --abbrev, but how\ndo I tell diff to stop abbreviating?\n\nAnd what should the documentation really say?\n\n-- \nDavid Kågedal\n"},{"id":"119084","messageId":"1cd1989b0907291029r2efd78br3506ded03dedf438@mail.gmail.com","threadId":"20250","inReplyTo":"873a8fflt2.fsf@krank.kagedal.org","subject":"Re: Output from git diff","fromName":"Pat Notz","fromEmail":"patnotz@gmail.com","sentAt":"2009-07-29T17:29:02Z","receivedAt":"2009-07-29T17:29:02Z","isPatch":false,"sender":{"key":"patnotz@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45364?v=4"},"body":"On Wed, Jul 29, 2009 at 11:20 AM, David Kågedal<davidk@lysator.liu.se> wrote:\n> Here is another diff output question. The updated documentation in\n> diff-format.txt still claims that the output from the diff commands\n> has this format:\n>\n> :100644 100644 bcd1234... 0123456... M file0\n>\n> This is true for \"git diff --raw\", but diff-tree and friends print\n> full 40-char hashes.\n>\n> I can get diff-tree to use abbreviated hashes with --abbrev, but how\n> do I tell diff to stop abbreviating?\n\nProbably not the answer you *really* want but 'git diff --raw\n--abbrev=40' will give you the full sha1\n\n>\n> And what should the documentation really say?\n>\n> --\n> David Kågedal\n>\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at  http://vger.kernel.org/majordomo-info.html\n>\n"},{"id":"119086","messageId":"7vab2nuyz3.fsf@alter.siamese.dyndns.org","threadId":"20250","inReplyTo":"873a8fflt2.fsf@krank.kagedal.org","subject":"Re: Output from git diff","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-07-29T18:26:56Z","receivedAt":"2009-07-29T18:26:56Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"David Kågedal <davidk@lysator.liu.se> writes:\n\n> And what should the documentation really say?\n\n\"git diff\" unlike \"git diff-<whatiscompared>\" is a Porcelain, to produce\nhuman-readable output, and defaults to the abbreviated form.\n"},{"id":"119161","messageId":"7v7hxqh9wu.fsf@alter.siamese.dyndns.org","threadId":"20250","inReplyTo":"87y6q6ehx8.fsf@krank.kagedal.org","subject":"Re: Output from git diff","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-07-30T08:06:41Z","receivedAt":"2009-07-30T08:06:41Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"David Kågedal <davidk@lysator.liu.se> writes:\n\n> Or perhaps the --raw flag to git diff isn't really meant to ever be\n> used?\n\nI do not think \"git diff\" Porcelain had --raw originally.\n\nIf you really need to know, you would need to dig the archives yourself,\nsorry.\n"}]}