From: Luben Tuikov <luben.tuikov@amd.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Michael Strawbridge" <michael.strawbridge@amd.com>,
"git@vger.kernel.org" <git@vger.kernel.org>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: Fwd: [PATCH v10 0/2] Expose header information to git-send-email's sendemail-validate hook
Date: Mon, 1 May 2023 21:05:29 -0400 [thread overview]
Message-ID: <fae69ed7-5b5b-0920-73f2-a0e72795c032@amd.com> (raw)
In-Reply-To: <41F7913A-E91B-4442-9531-5EE8EC2CAA9E@yahoo.com>
On 2023-05-01 21:01, Luben Tuikov wrote:
> Begin forwarded message:
>
>> *From:* Junio C Hamano <gitster@pobox.com>
>> *Date:* May 1, 2023 at 17:58:41 EDT
>> *To:* Michael Strawbridge <michael.strawbridge@amd.com>
>> *Cc:* git@vger.kernel.org, Luben Tuikov <ltuikov@yahoo.com>, Ævar Arnfjörð Bjarmason <avarab@gmail.com>
>> *Subject:* *Re: [PATCH v10 0/2] Expose header information to git-send-email's sendemail-validate hook*
>>
>> Michael Strawbridge <michael.strawbridge@amd.com> writes:
>>
>>> My appologies for taking a while to get back to this. Here is a reroll
>>> with the latest suggestions from Luben.
>>>
>>> Michael Strawbridge (2):
>>> send-email: refactor header generation functions
>>> send-email: expose header information to git-send-email's
>>> sendemail-validate hook
>>
>> This round did not see any further comments. Is everybody happy to
>> see us declare victory on this front and merge it down to 'next'?
>>
>> The topic does not make itself a reply to previous iterations, and
>> the cover letter does not CC: anybody who gave reviews to earlier
>> rounds, so it is a bit hard to answer the above question myself,
>> unfortunately. I manually picked off a few names after finding v9
>> and v8 from the list archive and added them to Cc: of this message.
>>
>> Thanks.
Sounds good to me.
--
Regards,
Luben
next prev parent reply other threads:[~2023-05-02 1:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 20:27 [PATCH v10 0/2] Expose header information to git-send-email's sendemail-validate hook Michael Strawbridge
2023-04-19 20:27 ` [PATCH v10 1/2] send-email: refactor header generation functions Michael Strawbridge
2023-04-19 20:27 ` [PATCH v10 2/2] send-email: expose header information to git-send-email's sendemail-validate hook Michael Strawbridge
2023-04-21 5:27 ` Luben Tuikov
2023-05-01 21:58 ` [PATCH v10 0/2] Expose " Junio C Hamano
[not found] ` <41F7913A-E91B-4442-9531-5EE8EC2CAA9E@yahoo.com>
2023-05-02 1:05 ` Luben Tuikov [this message]
2023-05-02 18:56 ` Fwd: " Michael Strawbridge
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=fae69ed7-5b5b-0920-73f2-a0e72795c032@amd.com \
--to=luben.tuikov@amd.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=michael.strawbridge@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).