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

Re: [PATCH 6/6] doc: patch-id: --verbatim locks in --stable

From
Pushkar Singh <pushkarkumarsingh1970@gmail.com>
Date
Jan 8, 2026, 18:15 UTC
Message-ID
<CALE2CrSu-JW___Lav0SnLPfwxB8QCRYMKQgsfbXCHrAQSEyDoA@mail.gmail.com>
In-Reply-To
<--verbatim_and_--stable.1b1@msgid.xyz>
Hi Kristoffer,
I read through the entire series and all six changes look correct to me.

Each patch is small and focused, and together they improve the clarity, consistency, and accuracy of the git-patch-id documentation without changing meaning. In particular, spelling out the `git diff-tree --patch` form and documenting the `--verbatim` / `--stable` relationship help align the docs more closely with the actual behavior and existing code.

I didn’t notice any issues with the changes.

Thanks for working on this, Pushkar

On Thu, Jan 8, 2026 at 12:02 PM <kristofferhaugsbakk@fastmail.com> wrote:
Show 36 quoted lines
>
> 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
>
>
Previous: kristofferhaugsbakk@fastmail.comNext: Kristoffer Haugsbakk
Message 8 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.