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

[PATCH 3/6] patch-id: use “patch ID” throughout

From
Kkristofferhaugsbakk@fastmail.com <kristofferhaugsbakk@fastmail.com>
Date
Jan 8, 2026, 06:28 UTC
Message-ID
<patch_ID_term.1ae@msgid.xyz>
In-Reply-To
<CV_doc_patch-id_3.1ab@msgid.xyz>
From: Kristoffer Haugsbakk <code@khaugsbakk.name>

The “Description” section decided to introduce and use the term “patch ID” for the ID value itself. Let’s use the same term on the options as well.

Also make to sure to use bare “ID” instead of “id”.
Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
---
 Documentation/git-patch-id.adoc | 10 +++++-----
 builtin/patch-id.c              |  4 ++--
 2 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/Documentation/git-patch-id.adoc b/Documentation/git-patch-id.adoc
index 82992e35fc1..9999f164b58 100644
--- a/Documentation/git-patch-id.adoc
+++ b/Documentation/git-patch-id.adoc
@@ -31,7 +31,7 @@ OPTIONS
 -------
 
 `--verbatim`::
-	Calculate the patch-id of the input as it is given, do not strip
+	Calculate the patch ID of the input as it is given, do not strip
 	any whitespace.
 +
 This is the default if `patchid.verbatim` is `true`.
@@ -51,18 +51,18 @@ This is the default if `patchid.verbatim` is `true`.
   or produced when an "unstable" hash (see `--unstable` below) is
   configured - even when used on a diff output taken without any use
   of `-O<orderfile>`, thereby making existing databases storing such
-  "unstable" or historical patch-ids unusable.
+  "unstable" or historical patch IDs unusable.
 
-- All whitespace within the patch is ignored and does not affect the id.
+- All whitespace within the patch is ignored and does not affect the ID.
 --
 +
 This is the default if `patchid.stable` is set to `true`.
 
 `--unstable`::
 	Use an "unstable" hash as the patch ID. With this option,
-	the result produced is compatible with the patch-id value produced
+	the result produced is compatible with the patch ID value produced
 	by Git 1.9 and older and whitespace is ignored.  Users with pre-existing
-	databases storing patch-ids produced by Git 1.9 and older (who do not deal
+	databases storing patch IDs produced by Git 1.9 and older (who do not deal
 	with reordered patches) may want to use this option.
 +
 This is the default.
diff --git a/builtin/patch-id.c b/builtin/patch-id.c
index d26e9d0c1ea..2781598ede6 100644
--- a/builtin/patch-id.c
+++ b/builtin/patch-id.c
@@ -228,9 +228,9 @@ int cmd_patch_id(int argc,
 	int opts = 0;
 	struct option builtin_patch_id_options[] = {
 		OPT_CMDMODE(0, "unstable", &opts,
-		    N_("use the unstable patch-id algorithm"), 1),
+		    N_("use the unstable patch ID algorithm"), 1),
 		OPT_CMDMODE(0, "stable", &opts,
-		    N_("use the stable patch-id algorithm"), 2),
+		    N_("use the stable patch ID algorithm"), 2),
 		OPT_CMDMODE(0, "verbatim", &opts,
 			N_("don't strip whitespace from the patch"), 3),
 		OPT_END()
-- 
2.52.0.421.gc32ead4fc78
Previous: kristofferhaugsbakk@fastmail.comNext: kristofferhaugsbakk@fastmail.com
Message 4 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.