From a77a9222127b6e873ffab08dd57bd5d37b069f41 Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Fri, 28 Oct 2005 02:39:56 -0700 Subject: [PATCH] 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 --- Documentation/git-patch-id.txt | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Documentation/git-patch-id.txt b/Documentation/git-patch-id.txt index 3e560a37..c8bd1977 100644 --- a/Documentation/git-patch-id.txt +++ b/Documentation/git-patch-id.txt @@ -18,6 +18,12 @@ ID" are almost guaranteed to be the same thing. IOW, you can use this thing to look for likely duplicate commits. +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. +This can be used to make a mapping from patch ID to commit ID. + OPTIONS ------- :: -- 2.11.0