Merge branch 'maint-1.6.0' into maint-1.6.1

[git.git] / Documentation / git-patch-id.txt

diff --git a/Documentation/git-patch-id.txt b/Documentation/git-patch-id.txt
index a7e9fd021a4cc1e467b2df7dd7e06d79a5182c7a..477785e13418e1971156f5210015da4ab9d77cab 100644 (file)
--- a/Documentation/git-patch-id.txt
+++ b/Documentation/git-patch-id.txt
@@ -7,7 +7,7 @@ git-patch-id - Compute unique ID for a patch
 
 SYNOPSIS
 --------
 
 SYNOPSIS
 --------

-'git-patch-id' < <patch>
+'git patch-id' < <patch>

 
 DESCRIPTION
 -----------
 
 DESCRIPTION
 -----------


@@ -18,7 +18,7 @@ ID" are almost guaranteed to be the same thing.
 
 IOW, you can use this thing to look for likely duplicate commits.
 
 
 IOW, you can use this thing to look for likely duplicate commits.
 

-When dealing with git-diff-tree output, it takes advantage of
+When dealing with 'git-diff-tree' output, it takes advantage of

 the fact that the patch is prefixed with the object name of the
 commit, and outputs two 40-byte hexadecimal string.  The first
 string is the patch ID, and the second string is the commit ID.
 the fact that the patch is prefixed with the object name of the
 commit, and outputs two 40-byte hexadecimal string.  The first
 string is the patch ID, and the second string is the commit ID.


@@ -39,5 +39,4 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 
 GIT
 ---
 
 GIT
 ---

-Part of the gitlink:git[7] suite
-
+Part of the linkgit:git[1] suite