Document git-patch-id a bit better.
Pavel Roskin wondered what the SHA1 output at the beginning of git-diff-tree was about. The only consumer of that information so far is this git-patch-id command, which was inadequately documented. Signed-off-by: Junio C Hamano <junkio@cox.net>
Junio C Hamano committed
Oct 28, 2005 at 02:39 UTC
a77a9222127b6e873ffab08dd57bd5d37b069f41
1 file changed
+6
Documentation/git-patch-id.txt
+6
@@ -18,6 +18,12 @@ ID" are almost guaranteed to be the same thing.
18
19
IOW, you can use this thing to look for likely duplicate commits.
20
21
+When dealing with git-diff-tree output, it takes advantage of
22
+the fact that the patch is prefixed with the object name of the
23
+commit, and outputs two 40-byte hexadecimal string. The first
24
+string is the patch ID, and the second string is the commit ID.
25
+This can be used to make a mapping from patch ID to commit ID.
26
+
27
OPTIONS
28
-------
29
<patch>::