git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 5/6] doc: patch-id: spell out the git-diff-tree(1) form

From
Kkristofferhaugsbakk@fastmail.com <kristofferhaugsbakk@fastmail.com>
Date
Jan 8, 2026, 06:28 UTC
Message-ID
<git_diff-tree_--patch.1b0@msgid.xyz>
In-Reply-To
<CV_doc_patch-id_3.1ab@msgid.xyz>
From: Kristoffer Haugsbakk <code@khaugsbakk.name>
You specifically need `--patch` since the default output is a raw diff.
Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
---
 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
Previous: kristofferhaugsbakk@fastmail.comNext: kristofferhaugsbakk@fastmail.com
Message 6 of 20 in “doc: patch-id: six small improvements”
  1. 0/6 doc: patch-id: six small improvementskristofferhaugsbakk@fastmail.com, Jan 8, 2026
  2. 1/6 doc: patch-id: don’t use semicolon between bullet pointskristofferhaugsbakk@fastmail.com, Jan 8, 2026
  3. 2/6 doc: patch-id: capitalize Git versionkristofferhaugsbakk@fastmail.com, Jan 8, 2026
  4. 3/6 patch-id: use “patch ID” throughoutkristofferhaugsbakk@fastmail.com, Jan 8, 2026
  5. 4/6 doc: patch-id: use definite article for the resultkristofferhaugsbakk@fastmail.com, Jan 8, 2026
  6. 5/6 doc: patch-id: spell out the git-diff-tree(1) formkristofferhaugsbakk@fastmail.com, Jan 8, 2026
  7. 6/6 doc: patch-id: --verbatim locks in --stablekristofferhaugsbakk@fastmail.com, Jan 8, 2026
  8. Pushkar SinghJan 8, 2026
  9. Kristoffer HaugsbakkJan 8, 2026
  10. Kristoffer HaugsbakkJan 8, 2026
  11. Patrick SteinhardtJan 9, 2026
  12. Kristoffer HaugsbakkJan 9, 2026
  13. 0/6 doc: patch-id: six small improvementskristofferhaugsbakk@fastmail.com, Jan 9, 2026
  14. 1/6 doc: patch-id: don’t use semicolon between bullet pointskristofferhaugsbakk@fastmail.com, Jan 9, 2026
  15. 2/6 doc: patch-id: capitalize Git versionkristofferhaugsbakk@fastmail.com, Jan 9, 2026
  16. 3/6 patch-id: use “patch ID” throughoutkristofferhaugsbakk@fastmail.com, Jan 9, 2026
  17. 4/6 doc: patch-id: use definite article for the resultkristofferhaugsbakk@fastmail.com, Jan 9, 2026
  18. 5/6 doc: patch-id: spell out the git-diff-tree(1) formkristofferhaugsbakk@fastmail.com, Jan 9, 2026
  19. 6/6 doc: patch-id: --verbatim locks in --stablekristofferhaugsbakk@fastmail.com, Jan 9, 2026
  20. Patrick SteinhardtJan 9, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.