Code

diff documentation: mostly talk about <commit>
authorJunio C Hamano <junkio@cox.net>
Wed, 20 Dec 2006 22:41:54 +0000 (14:41 -0800)
committerJunio C Hamano <junkio@cox.net>
Wed, 20 Dec 2006 22:41:54 +0000 (14:41 -0800)
This corrects minor remaining bits that still talked about <tree-ish>;
the Porcelain users (as opposed to plumbers) are mostly interested in
commits so use <commit> consistently and keep a sentence that mentions
that <tree-ish> can be used in place of them.

Documentation/git-diff.txt

index 10fdf88dce296f9fd7aea849b974cfbe709fa1b4..8977877b21b6681528d13f71b558c060e8c26c4d 100644 (file)
@@ -8,7 +8,7 @@ git-diff - Show changes between commits, commit and working tree, etc
 
 SYNOPSIS
 --------
-'git-diff' [ --diff-options ] <tree-ish>{0,2} [--] [<path>...]
+'git-diff' [ --diff-options ] <commit>{0,2} [--] [<path>...]
 
 DESCRIPTION
 -----------
@@ -26,7 +26,7 @@ tree and the index file, or the index file and the working tree.
 'git-diff' [--options] --cached [<commit>] [--] [<path>...]::
 
        This form is to view the changes you staged for the next
-       commit relative to the named <tree-ish>.  Typically you
+       commit relative to the named <commit>.  Typically you
        would want comparison with the latest commit, so if you
        do not give <commit>, it defaults to HEAD.