git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org, "Strawbridge,
	Michael" <Michael.Strawbridge@amd.com>
Subject: ms/sendemail-validate-headers, was Re: What's cooking in git.git (Nov 2022, #03; Mon, 14)
Date: Tue, 15 Nov 2022 15:04:29 +0100 (CET)	[thread overview]
Message-ID: <4p90qnq3-580o-9n59-34n0-rs3pp635908o@tzk.qr> (raw)
In-Reply-To: <Y3Mag8qG2D3qjlmg@nand.local>

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"?

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").

Ciao,
Johannes

  parent reply	other threads:[~2022-11-15 14:05 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 ` Johannes Schindelin [this message]
2022-11-16  1:20   ` ms/sendemail-validate-headers, was Re: What's cooking in git.git (Nov 2022, #03; Mon, 14) Taylor Blau
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=4p90qnq3-580o-9n59-34n0-rs3pp635908o@tzk.qr \
    --to=johannes.schindelin@gmx.de \
    --cc=Michael.Strawbridge@amd.com \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylorr.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. 
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).