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

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

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 20, 2026, 22:31 UTC
Message-ID
<xmqq1pifvyhm.fsf@gitster.g>
In-Reply-To
<V2_CV_doc_patch-id_4.371@msgid.xyz>
kristofferhaugsbakk@fastmail.com writes:
Show 8 quoted lines
> 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.
>
> § Changes in v2
>
> • Delete temporary files at the end of the script.
> • Consistent footnote style: https://lore.kernel.org/git/c70adde6-e3db-4a46-bb29-a19d7aba8c7e@app.fastmail.com/

The latest iteration of this series has seen no responses. Is everybody happy with them?

Thanks.
Previous: Ben KnobleNext: Ben Knoble
Message 13 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.