From: Kristoffer Haugsbakk <code@khaugsbakk.name>
Date: Thu, 08 Jan 2026 18:26:51 GMT
Subject: Re: [PATCH 6/6] doc: patch-id: --verbatim locks in --stable
Message-ID: <52c8f9e2-2287-4a0f-a262-869562cb5695@app.fastmail.com>
In-Reply-To: <--verbatim_and_--stable.1b1@msgid.xyz>

On Thu, Jan 8, 2026, at 07:28, kristofferhaugsbakk@fastmail.com wrote:
> 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

s/`--unstable/`--unstable`/

>
> Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
> ---
>[snip]