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

Re: [PATCH 0/3] doc: patch-id: explain how to map efficiently

From
D. Ben Knoble <ben.knoble@gmail.com>
Date
Feb 8, 2026, 02:34 UTC
Message-ID
<CALnO6CBnGf6M=a__5mbGNFZ--kDj45nzFBpsv-jPcwO-e5ThOQ@mail.gmail.com>
In-Reply-To
<CV_doc_patch-id_4.275@msgid.xyz>
On Sat, Feb 7, 2026 at 10:06 AM <kristofferhaugsbakk@fastmail.com> wrote:
Show 34 quoted lines
>
> From: Kristoffer Haugsbakk <code@khaugsbakk.name>
>
> Topic name: kh/doc-patch-id-4
>
> Topic summary: Explain and emphasize how to map commits efficiently and
> add an example script.
>
> This is the fourth patch series for git-patch-id(1). This one focuses on
> emphasizing how the command is an efficient patch ID–commit mapper and
> how to use the patch IDs to join commits in a script.
>
> • Patch series 1:
>   • Topic: kh/doc-patch-id-markup-fix
>   • https://lore.kernel.org/git/v2-e5ad12cc3b3.1759178715.git.code@khaugsbakk.name/
> • Patch series 2:
>   • Topic: kh/doc-patch-id-1
>   • https://lore.kernel.org/git/v2-38645ea253c.1760369708.git.code@khaugsbakk.name/
> • Patch series 3:
>   • Topic: kh/doc-patch-id
>   • https://lore.kernel.org/git/CV_doc_patch-id_3.1ab@msgid.xyz/
>
> Kristoffer Haugsbakk (3):
>   doc: patch-id: emphasize multi-patch processing
>   doc: patch-id: add script example
>   doc: patch-id: see also git-cherry(1)
>
>  Documentation/git-patch-id.adoc | 49 +++++++++++++++++++++++++++++++--
>  1 file changed, 46 insertions(+), 3 deletions(-)
>
>
> base-commit: 67ad42147a7acc2af6074753ebd03d904476118f
> --
> 2.53.0.26.g2afa8602a26

Short and sweet with a nice demo of how to use git-patch-id(1). One nit on the script, but otherwise LGTM.

-- D. Ben Knoble

Previous: kristofferhaugsbakk@fastmail.comNext: kristofferhaugsbakk@fastmail.com
Message 7 of 15 in “doc: patch-id: explain how to map efficiently”
  1. 0/3 doc: patch-id: explain how to map efficientlykristofferhaugsbakk@fastmail.com, Feb 7, 2026
  2. 1/3 doc: patch-id: emphasize multi-patch processingkristofferhaugsbakk@fastmail.com, Feb 7, 2026
  3. 2/3 doc: patch-id: add script examplekristofferhaugsbakk@fastmail.com, Feb 7, 2026
  4. D. Ben KnobleFeb 8, 2026
  5. Kristoffer HaugsbakkFeb 8, 2026
  6. 3/3 doc: patch-id: see also git-cherry(1)kristofferhaugsbakk@fastmail.com, Feb 7, 2026
  7. D. Ben KnobleFeb 8, 2026
  8. 0/3 doc: patch-id: explain how to map efficientlykristofferhaugsbakk@fastmail.com, Feb 14, 2026
  9. 1/3 doc: patch-id: emphasize multi-patch processingkristofferhaugsbakk@fastmail.com, Feb 14, 2026
  10. 2/3 doc: patch-id: add script examplekristofferhaugsbakk@fastmail.com, Feb 14, 2026
  11. 3/3 doc: patch-id: see also git-cherry(1)kristofferhaugsbakk@fastmail.com, Feb 14, 2026
  12. Ben KnobleFeb 14, 2026
  13. Junio C HamanoFeb 20, 2026
  14. Ben KnobleFeb 21, 2026
  15. Kristoffer HaugsbakkFeb 23, 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.