From: D. Ben Knoble Date: Sun, 08 Feb 2026 02:34:12 GMT Subject: Re: [PATCH 0/3] doc: patch-id: explain how to map efficiently Message-ID: In-Reply-To: On Sat, Feb 7, 2026 at 10:06 AM wrote: > > From: Kristoffer Haugsbakk > > 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