diff options
| author | Kristoffer Haugsbakk <code@khaugsbakk.name> | 2026-01-08 07:28:19 +0100 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2026-01-09 06:07:22 -0800 |
| commit | 89d4f3af16a95fe1b6abe8c9f43fb7fb6826dadf (patch) | |
| tree | 9a07dec1116e5f04163ee1a2b2ffd60697a8bcbf | |
| parent | f671f5a83b78643964bdfb75eb0aab54d23e25e9 (diff) | |
| download | git-89d4f3af16a95fe1b6abe8c9f43fb7fb6826dadf.tar.xz | |
doc: patch-id: spell out the git-diff-tree(1) form
You specifically need `--patch` since the default output is a raw diff.
Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| -rw-r--r-- | Documentation/git-patch-id.adoc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/git-patch-id.adoc b/Documentation/git-patch-id.adoc index abd02fccdc..61498def31 100644 --- a/Documentation/git-patch-id.adoc +++ b/Documentation/git-patch-id.adoc @@ -21,7 +21,7 @@ the same time also reasonably unique, i.e., two patches that have the same The main usecase for this command is to look for likely duplicate commits. -When dealing with `git diff-tree` output, it takes advantage of +When dealing with `git diff-tree --patch` 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. |