[PATCH 6/6] doc: patch-id: --verbatim locks in --stable
- From
- kristofferhaugsbakk@fastmail.com <kristofferhaugsbakk@fastmail.com>
- Date
- Jan 8, 2026, 06:28 UTC
- Message-ID
- <--verbatim_and_--stable.1b1@msgid.xyz>
- 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