summaryrefslogtreecommitdiffstats
path: root/git-patch-id.html
diff options
context:
space:
mode:
authorJunio C Hamano <junio@hera.kernel.org>2008-07-02 03:06:38 +0000
committerJunio C Hamano <junio@hera.kernel.org>2008-07-02 03:06:38 +0000
commitfce7c7e1549d1a2a2b0faf5952378236eed4d468 (patch)
treeffce2ae419b52786a0e567f4fddaadd89016f62c /git-patch-id.html
parentbb8e996adf4293a0b624fe77e95e12ae8d1faed9 (diff)
downloadgit-htmldocs-fce7c7e1549d1a2a2b0faf5952378236eed4d468.tar.gz
Autogenerated HTML docs for v1.5.6.1-156-ge903b
Diffstat (limited to 'git-patch-id.html')
-rw-r--r--git-patch-id.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/git-patch-id.html b/git-patch-id.html
index e5a8f869b..0e4645c81 100644
--- a/git-patch-id.html
+++ b/git-patch-id.html
@@ -272,7 +272,7 @@ git-patch-id(1) Manual Page
</div>
<h2>SYNOPSIS</h2>
<div class="sectionbody">
-<p><em>git-patch-id</em> &lt; &lt;patch&gt;</p>
+<p><em>git patch-id</em> &lt; &lt;patch&gt;</p>
</div>
<h2>DESCRIPTION</h2>
<div class="sectionbody">
@@ -281,7 +281,7 @@ whitespace and line numbers ignored. As such, it's "reasonably stable", but at
the same time also reasonably unique, i.e., two patches that have the same "patch
ID" are almost guaranteed to be the same thing.</p>
<p>IOW, you can use this thing to look for likely duplicate commits.</p>
-<p>When dealing with git-diff-tree output, it takes advantage of
+<p>When dealing with <tt>git-diff-tree</tt> 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.
@@ -314,7 +314,7 @@ This can be used to make a mapping from patch ID to commit ID.</p>
</div>
<div id="footer">
<div id="footer-text">
-Last updated 08-Jun-2008 01:33:59 UTC
+Last updated 02-Jul-2008 03:01:55 UTC
</div>
</div>
</body>