From: kristofferhaugsbakk@fastmail.com Date: Thu, 08 Jan 2026 06:28:19 GMT Subject: [PATCH 5/6] doc: patch-id: spell out the git-diff-tree(1) form Message-ID: In-Reply-To: From: Kristoffer Haugsbakk You specifically need `--patch` since the default output is a raw diff. Signed-off-by: Kristoffer Haugsbakk --- Documentation/git-patch-id.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/git-patch-id.adoc b/Documentation/git-patch-id.adoc index abd02fccdc0..61498def317 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. -- 2.52.0.421.gc32ead4fc78