From: kristofferhaugsbakk@fastmail•com
To: git@vger•kernel.org
Cc: Kristoffer Haugsbakk <code@khaugsbakk•name>
Subject: [PATCH 6/6] doc: patch-id: --verbatim locks in --stable
Date: Thu, 8 Jan 2026 07:28:20 +0100 [thread overview]
Message-ID: <--verbatim_and_--stable.1b1@msgid.xyz> (raw)
In-Reply-To: <CV_doc_patch-id_3.1ab@msgid.xyz>
From: Kristoffer Haugsbakk <code@khaugsbakk•name>
The default `--unstable` is a legacy format that predates `--stable`.
That’s why 2871f4d4 (builtin: patch-id: add --verbatim as a command mode,
2022-10-24) made `--verbatim` lock in[1] `--stable`:
Users of --unstable mainly care about compatibility with old git
versions, which unstripping the whitespace would break. Thus there
isn't a usecase for the combination of --verbatim and --unstable,
and we don't expose this so as to not add maintainence burden.
† 1: imply `--stable`, disallow `--unstable
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 61498def317..013e1a61906 100644
--- a/Documentation/git-patch-id.adoc
+++ b/Documentation/git-patch-id.adoc
@@ -32,7 +32,7 @@ OPTIONS
`--verbatim`::
Calculate the patch ID of the input as it is given, do not strip
- any whitespace.
+ any whitespace. Implies `--stable` and forbids `--unstable`.
+
This is the default if `patchid.verbatim` is `true`.
--
2.52.0.421.gc32ead4fc78
next prev parent reply other threads:[~2026-01-08 6:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 6:28 [PATCH 0/6] doc: patch-id: six small improvements kristofferhaugsbakk
2026-01-08 6:28 ` [PATCH 1/6] doc: patch-id: don’t use semicolon between bullet points kristofferhaugsbakk
2026-01-08 6:28 ` [PATCH 2/6] doc: patch-id: capitalize Git version kristofferhaugsbakk
2026-01-08 6:28 ` [PATCH 3/6] patch-id: use “patch ID” throughout kristofferhaugsbakk
2026-01-08 6:28 ` [PATCH 4/6] doc: patch-id: use definite article for the result kristofferhaugsbakk
2026-01-08 6:28 ` [PATCH 5/6] doc: patch-id: spell out the git-diff-tree(1) form kristofferhaugsbakk
2026-01-08 6:28 ` kristofferhaugsbakk [this message]
2026-01-08 18:15 ` [PATCH 6/6] doc: patch-id: --verbatim locks in --stable Pushkar Singh
2026-01-08 18:18 ` Kristoffer Haugsbakk
2026-01-08 18:26 ` Kristoffer Haugsbakk
2026-01-09 11:38 ` [PATCH 0/6] doc: patch-id: six small improvements Patrick Steinhardt
2026-01-09 11:45 ` Kristoffer Haugsbakk
2026-01-09 14:25 ` [PATCH v2 " kristofferhaugsbakk
2026-01-09 14:25 ` [PATCH v2 1/6] doc: patch-id: don’t use semicolon between bullet points kristofferhaugsbakk
2026-01-09 14:25 ` [PATCH v2 2/6] doc: patch-id: capitalize Git version kristofferhaugsbakk
2026-01-09 14:25 ` [PATCH v2 3/6] patch-id: use “patch ID” throughout kristofferhaugsbakk
2026-01-09 14:26 ` [PATCH v2 4/6] doc: patch-id: use definite article for the result kristofferhaugsbakk
2026-01-09 14:26 ` [PATCH v2 5/6] doc: patch-id: spell out the git-diff-tree(1) form kristofferhaugsbakk
2026-01-09 14:26 ` [PATCH v2 6/6] doc: patch-id: --verbatim locks in --stable kristofferhaugsbakk
2026-01-09 14:55 ` [PATCH v2 0/6] doc: patch-id: six small improvements Patrick Steinhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=--verbatim_and_--stable.1b1@msgid.xyz \
--to=kristofferhaugsbakk@fastmail$(echo .)com \
--cc=code@khaugsbakk$(echo .)name \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox