diff options
| author | Junio C Hamano <junio@hera.kernel.org> | 2006-06-04 07:24:48 +0000 |
|---|---|---|
| committer | Junio C Hamano <junio@hera.kernel.org> | 2006-06-04 07:24:48 +0000 |
| commit | 341071d878757c06a3931db660fe318effc8317e (patch) | |
| tree | 8cb7bf28351c062adbe71172b942a3228d40725d /git-patch-id.html | |
| parent | bb8fb05ed082c81af81f9eecf356f993e2ef83b7 (diff) | |
| download | git-htmldocs-341071d878757c06a3931db660fe318effc8317e.tar.gz | |
Autogenerated HTML docs for v1.3.3-g16a4
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 1ac007088..1ce76f446 100644 --- a/git-patch-id.html +++ b/git-patch-id.html @@ -278,7 +278,7 @@ git-patch-id(1) Manual Page <div class="sectionbody">
<p>A "patch ID" is nothing but a SHA1 of the diff associated with a patch, with
whitespace and line numbers ignored. As such, it's "reasonably stable", but at
-the same time also reasonably unique, ie two patches that have the same "patch
+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
@@ -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 10-Mar-2006 00:31:30 UTC
+Last updated 04-Jun-2006 07:24:28 UTC
</div>
</div>
</body>
|