From: Taylor Blau <me@ttaylorr.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Taylor Blau <me@ttaylorr.com>,
git@vger.kernel.org, "Strawbridge,
Michael" <Michael.Strawbridge@amd.com>
Subject: Re: ms/sendemail-validate-headers, was Re: What's cooking in git.git (Nov 2022, #03; Mon, 14)
Date: Tue, 15 Nov 2022 20:20:53 -0500 [thread overview]
Message-ID: <Y3Q69UlrmyCXLCsY@nand.local> (raw)
In-Reply-To: <4p90qnq3-580o-9n59-34n0-rs3pp635908o@tzk.qr>
On Tue, Nov 15, 2022 at 03:04:29PM +0100, Johannes Schindelin wrote:
> Hi Taylor,
>
> On Mon, 14 Nov 2022, Taylor Blau wrote:
>
> > * ms/sendemail-validate-headers (2022-11-11) 1 commit
> > - Expose header information to git-send-email's sendemail-validate hook
> >
> > Expecting a reroll.
> > source: <20221111194223.644845-2-michael.strawbridge@amd.com>
>
> I see this mail, but no replies. Is it really appropriate to label this as
> "Expecting a reroll"?
Thanks for spotting. I wrote this one from memory, but in retrospect I
think I was thinking of a different thread [1] between the patch author
and brian where there was some discussion (but no patches).
> A more appropriate label would be "Breaks t9001", I would think, and the
> reference should probable be <36s0r4s9-n21r-pop9-o7rn-q0qrq487p831@tzk.qr>
> instead (but I sent that out only a couple of minutes ago, so I would
> still be curious why it was marked as "Expecting a reroll").
Yes, let's keep this out of 'seen' since it has seen no review and
breaks t9001. I'll update my notes accordingly, thanks.
Thanks,
Taylor
[1]: https://lore.kernel.org/git/87czcm7maf.fsf@amd.com/#t
next prev parent reply other threads:[~2022-11-16 1:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 4:50 What's cooking in git.git (Nov 2022, #03; Mon, 14) Taylor Blau
2022-11-15 4:59 ` Eric Sunshine
2022-11-15 5:01 ` Taylor Blau
2022-11-15 6:28 ` ps/receive-use-only-advertised Patrick Steinhardt
2022-11-15 6:47 ` ps/receive-use-only-advertised Taylor Blau
2022-11-15 17:28 ` ps/receive-use-only-advertised Jeff King
2022-11-16 2:02 ` ps/receive-use-only-advertised Taylor Blau
2022-11-18 23:27 ` ps/receive-use-only-advertised Junio C Hamano
2022-11-15 8:06 ` rp/maintenance-qol with 'make DEVELOPER=1' (was: What's cooking in git.git (Nov 2022, #03; Mon, 14)) Ævar Arnfjörð Bjarmason
2022-11-15 14:04 ` ms/sendemail-validate-headers, was Re: What's cooking in git.git (Nov 2022, #03; Mon, 14) Johannes Schindelin
2022-11-16 1:20 ` Taylor Blau [this message]
2022-11-16 11:48 ` Strawbridge, Michael
2022-11-18 13:24 ` Johannes Schindelin
2022-11-15 20:58 ` Eric Sunshine
2022-11-16 2:04 ` Taylor Blau
2022-11-16 6:07 ` Elijah Newren
2022-11-16 20:16 ` Taylor Blau
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y3Q69UlrmyCXLCsY@nand.local \
--to=me@ttaylorr.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=Michael.Strawbridge@amd.com \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).