From: Ben Knoble <ben.knoble@gmail•com>
To: Junio C Hamano <gitster@pobox•com>
Cc: kristofferhaugsbakk@fastmail•com, git@vger•kernel.org,
Kristoffer Haugsbakk <code@khaugsbakk•name>,
Linus Torvalds <torvalds@linux-foundation•org>
Subject: Re: [PATCH v2 0/3] doc: patch-id: explain how to map efficiently
Date: Fri, 20 Feb 2026 21:38:15 -0500 [thread overview]
Message-ID: <F628C3EE-0600-419E-8D85-0CEA9EEA2243@gmail.com> (raw)
In-Reply-To: <xmqq1pifvyhm.fsf@gitster.g>
> 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, ;)
next prev parent reply other threads:[~2026-02-21 2:38 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 [this message]
2026-02-23 18:04 ` Kristoffer Haugsbakk
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=F628C3EE-0600-419E-8D85-0CEA9EEA2243@gmail.com \
--to=ben.knoble@gmail$(echo .)com \
--cc=code@khaugsbakk$(echo .)name \
--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