diff options
| author | Junio C Hamano <junkio@cox.net> | 2005-10-28 02:39:56 -0700 |
|---|---|---|
| committer | Junio C Hamano <junkio@cox.net> | 2005-10-28 02:39:56 -0700 |
| commit | a77a9222127b6e873ffab08dd57bd5d37b069f41 (patch) | |
| tree | 2874f270ac824f6751f034514af7eee98c6e4a38 | |
| parent | 6d0de319d6249096fe934317e937177d07b1b84f (diff) | |
| download | git-a77a9222127b6e873ffab08dd57bd5d37b069f41.tar.gz git-a77a9222127b6e873ffab08dd57bd5d37b069f41.tar.xz | |
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>
| -rw-r--r-- | Documentation/git-patch-id.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/Documentation/git-patch-id.txt b/Documentation/git-patch-id.txt index 3e560a37e..c8bd19777 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 ------- <patch>:: |