diff options
| author | Junio C Hamano <junio@kernel.org> | 2010-01-21 17:46:43 +0000 |
|---|---|---|
| committer | Junio C Hamano <junio@kernel.org> | 2010-01-21 17:46:43 +0000 |
| commit | 1aa40d2e3f5186afb805e7020577acb9f5f78b89 (patch) | |
| tree | 72812d480799e16b94f9cfed423b8d7d45c7fb4f /git-patch-id.html | |
| parent | a9701f0184382d8de7380c56558718915905746a (diff) | |
| download | git-htmldocs-1aa40d2e3f5186afb805e7020577acb9f5f78b89.tar.gz | |
Autogenerated HTML docs for v1.6.6.1-383-g5a9f
Diffstat (limited to 'git-patch-id.html')
| -rw-r--r-- | git-patch-id.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/git-patch-id.html b/git-patch-id.html index 96641b774..62edc3cae 100644 --- a/git-patch-id.html +++ b/git-patch-id.html @@ -329,7 +329,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></div>
<div class="para"><p>IOW, you can use this thing to look for likely duplicate commits.</p></div>
-<div class="para"><p>When dealing with <em>git-diff-tree</em> output, it takes advantage of
+<div class="para"><p>When dealing with <em>git diff-tree</em> 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 strings. The first
string is the patch ID, and the second string is the commit ID.
@@ -362,7 +362,7 @@ This can be used to make a mapping from patch ID to commit ID.</p></div> </div>
<div id="footer">
<div id="footer-text">
-Last updated 2009-12-03 09:12:43 UTC
+Last updated 2010-01-21 17:44:34 UTC
</div>
</div>
</body>
|