path: root/Documentation/git-diff-index.txt
diff options
authorAndy Parkins <>2006-11-02 11:12:44 (GMT)
committerJunio C Hamano <>2006-11-03 02:03:31 (GMT)
commit44b27ec9604b0310c4d24a283319b933a86da67d (patch)
tree5997f7975d60bbc754cddd252b1471ed63686f9f /Documentation/git-diff-index.txt
parent866cae0db4af936ec6f9eb6362e50db2a1a2f792 (diff)
Minor grammar fixes for git-diff-index.txt
"what you are going to commit is" doesn't need the "is" and does need a comma. "can trivially see" is an unecessary split infinitive and "easily" is a more appropriate adverb. Signed-off-by: Andy Parkins <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'Documentation/git-diff-index.txt')
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/git-diff-index.txt b/Documentation/git-diff-index.txt
index 9cd43f1..2df581c 100644
--- a/Documentation/git-diff-index.txt
+++ b/Documentation/git-diff-index.txt
@@ -54,7 +54,7 @@ If '--cached' is specified, it allows you to ask:
For example, let's say that you have worked on your working directory, updated
some files in the index and are ready to commit. You want to see exactly
-*what* you are going to commit is without having to write a new tree
+*what* you are going to commit, without having to write a new tree
object and compare it that way, and to do that, you just do
git-diff-index --cached HEAD
@@ -68,7 +68,7 @@ matches my working directory. But doing a "git-diff-index" does:
-100644 blob 4161aecc6700a2eb579e842af0b7f22b98443f74 commit.c
+100644 blob 4161aecc6700a2eb579e842af0b7f22b98443f74 git-commit.c
-You can trivially see that the above is a rename.
+You can see easily that the above is a rename.
In fact, "git-diff-index --cached" *should* always be entirely equivalent to
actually doing a "git-write-tree" and comparing that. Except this one is much