diff documentation: mostly talk about <commit>
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.
This commit is contained in:
parent
63c4b4c5c1
commit
ce0545455a
@ -8,7 +8,7 @@ git-diff - Show changes between commits, commit and working tree, etc
|
|||||||
|
|
||||||
SYNOPSIS
|
SYNOPSIS
|
||||||
--------
|
--------
|
||||||
'git-diff' [ --diff-options ] <tree-ish>{0,2} [--] [<path>...]
|
'git-diff' [ --diff-options ] <commit>{0,2} [--] [<path>...]
|
||||||
|
|
||||||
DESCRIPTION
|
DESCRIPTION
|
||||||
-----------
|
-----------
|
||||||
@ -26,7 +26,7 @@ tree and the index file, or the index file and the working tree.
|
|||||||
'git-diff' [--options] --cached [<commit>] [--] [<path>...]::
|
'git-diff' [--options] --cached [<commit>] [--] [<path>...]::
|
||||||
|
|
||||||
This form is to view the changes you staged for the next
|
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
|
would want comparison with the latest commit, so if you
|
||||||
do not give <commit>, it defaults to HEAD.
|
do not give <commit>, it defaults to HEAD.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user