{"thread":{"id":"43659","subject":"(unknown)","startedAt":"2006-10-25T14:49:35Z","lastAt":"2006-10-25T14:49:35Z","messageCount":1,"participants":["andyparkins@gmail.com"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"296405","messageId":"E1Gck4V-0003If-00@dvr.360vision.com","threadId":"43659","inReplyTo":null,"subject":"(unknown)","fromName":"","fromEmail":"andyparkins@gmail.com","sentAt":"2006-10-25T14:49:35Z","receivedAt":"2006-10-25T14:49:35Z","isPatch":false,"sender":{"key":"andyparkins@gmail.com","avatar":null},"body":"From cf13955d13b8b6a86dd1f6340565e16500b3cf38 Mon Sep 17 00:00:00 2001\nFrom: Andy Parkins <andyparkins@gmail.com>\nDate: Wed, 25 Oct 2006 15:49:34 +0100\nSubject: [PATCH] Minor grammar fixes for git-diff-index.txt\nTo: git@vger.kernel.org\nX-TUID: c63a7eaedc72a5ce\nX-UID: 129\nX-Length: 2247\nMIME-Version: 1.0\nContent-Transfer-Encoding: 7bit\nContent-Disposition: inline\nMessage-Id: <200610251549.34193.andyparkins@gmail.com>\n\n\"what you are going to commit is\" doesn't need the \"is\" and does need a comma.\n\n\"can trivially see\" is an unecessary split infinitive and \"easily\" is a more\nappropriate adverb.\n\n\"case where you\" should be \"case were you\" as it's the past tense form of the\nverb \"to be\", rather than a location (I think :-) ).\nSigned-off-by: Andy Parkins <andyparkins@gmail.com>\n---\n Documentation/git-diff-index.txt |    6 +++---\n 1 files changed, 3 insertions(+), 3 deletions(-)\n\ndiff --git a/Documentation/git-diff-index.txt \nb/Documentation/git-diff-index.txt\nindex 9cd43f1..ad1e903 100644\n--- a/Documentation/git-diff-index.txt\n+++ b/Documentation/git-diff-index.txt\n@@ -54,7 +54,7 @@ If '--cached' is specified, it allows yo\n \n For example, let's say that you have worked on your working directory, \nupdated\n some files in the index and are ready to commit. You want to see exactly\n-*what* you are going to commit is without having to write a new tree\n+*what* you are going to commit, without having to write a new tree\n object and compare it that way, and to do that, you just do\n \n \tgit-diff-index --cached HEAD\n@@ -68,11 +68,11 @@ matches my working directory. But doing \n   -100644 blob    4161aecc6700a2eb579e842af0b7f22b98443f74        commit.c\n   +100644 blob    4161aecc6700a2eb579e842af0b7f22b98443f74        \ngit-commit.c\n \n-You can trivially see that the above is a rename.\n+You can see easily that the above is a rename.\n \n In fact, \"git-diff-index --cached\" *should* always be entirely equivalent to\n actually doing a \"git-write-tree\" and comparing that. Except this one is much\n-nicer for the case where you just want to check where you are.\n+nicer for the case were you just want to check where you are.\n \n So doing a \"git-diff-index --cached\" is basically very useful when you are\n asking yourself \"what have I already marked for being committed, and \n-- \n1.4.2.3\n"}]}