Skip to content

Commit

Permalink
Minor grammar fixes for git-diff-index.txt
Browse files Browse the repository at this point in the history
"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 <andyparkins@gmail.com>
Signed-off-by: Junio C Hamano <junkio@cox.net>
  • Loading branch information
Andy Parkins authored and Junio C Hamano committed Nov 3, 2006
1 parent 866cae0 commit 44b27ec
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions Documentation/git-diff-index.txt
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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
Expand Down

0 comments on commit 44b27ec

Please sign in to comment.