From: "Kristoffer Haugsbakk" <code@khaugsbakk•name>
To: "D. Ben Knoble" <ben.knoble@gmail•com>,
"Junio C Hamano" <gitster@pobox•com>
Cc: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com>,
git@vger•kernel.org,
"Linus Torvalds" <torvalds@linux-foundation•org>
Subject: Re: [PATCH v2 0/3] doc: patch-id: explain how to map efficiently
Date: Mon, 23 Feb 2026 19:04:01 +0100 [thread overview]
Message-ID: <af41be2a-daac-4d23-852d-61ff7e0dae6d@app.fastmail.com> (raw)
In-Reply-To: <F628C3EE-0600-419E-8D85-0CEA9EEA2243@gmail.com>
On Sat, Feb 21, 2026, at 03:38, Ben Knoble wrote:
>> Le 20 févr. 2026 à 17:31, Junio C Hamano <gitster@pobox•com> a écrit :
>>
>> kristofferhaugsbakk@fastmail•com writes:
>>
>>> 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.
>
> No /further/ responses, perhaps? Unless my mail didn’t come through. I
> completely understand if my approval was not weighted particularly
> highly, though, ;)
Thanks for following this series.
I was wondering if a relatively lengthy example like that would be
accepted on such a small (doc footprint) command. I was ready to drop
that example patch/commit if the series didn’t move ahead.
In general *I* would like to see more examples and discussions in the
docs where commands that are better used in conjunction with other Git
commands and general utilities (c.f. git-commit(1), git-tag(1),
...). And in this case, this “write a script for it” command, as it was
called in the linked email,[1] seemed like a good candidate.
† 1: https://lore.kernel.org/workflows/CAHk-=wiN+8EUoik4UeAJ-HPSU7hczQP+8+_uP3vtAy_=YfJ9PQ@mail.gmail.com/
It’s a bit hard to find information on this on the Web, I think, because
“Git plumbing” has been SEO’ed into the silo of “here’s how you can use
three Git plumbing commands to do what you can do in one Git porcelain
command”.
But I also can understand if others think (maybe?) think that this would
be too much verbiage.
But I see that this is in `next` now. Which I am glad to see of course.
prev parent reply other threads:[~2026-02-23 18:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-07 15:05 [PATCH 0/3] doc: patch-id: explain how to map efficiently kristofferhaugsbakk
2026-02-07 15:05 ` [PATCH 1/3] doc: patch-id: emphasize multi-patch processing kristofferhaugsbakk
2026-02-07 15:05 ` [PATCH 2/3] doc: patch-id: add script example kristofferhaugsbakk
2026-02-08 2:34 ` D. Ben Knoble
2026-02-08 17:23 ` Kristoffer Haugsbakk
2026-02-07 15:05 ` [PATCH 3/3] doc: patch-id: see also git-cherry(1) kristofferhaugsbakk
2026-02-08 2:34 ` [PATCH 0/3] doc: patch-id: explain how to map efficiently D. Ben Knoble
2026-02-14 11:55 ` [PATCH v2 " kristofferhaugsbakk
2026-02-14 11:55 ` [PATCH v2 1/3] doc: patch-id: emphasize multi-patch processing kristofferhaugsbakk
2026-02-14 11:55 ` [PATCH v2 2/3] doc: patch-id: add script example kristofferhaugsbakk
2026-02-14 11:55 ` [PATCH v2 3/3] doc: patch-id: see also git-cherry(1) kristofferhaugsbakk
2026-02-14 20:00 ` [PATCH v2 0/3] doc: patch-id: explain how to map efficiently Ben Knoble
2026-02-20 22:31 ` Junio C Hamano
2026-02-21 2:38 ` Ben Knoble
2026-02-23 18:04 ` Kristoffer Haugsbakk [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=af41be2a-daac-4d23-852d-61ff7e0dae6d@app.fastmail.com \
--to=code@khaugsbakk$(echo .)name \
--cc=ben.knoble@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=kristofferhaugsbakk@fastmail$(echo .)com \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox