From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Gomez <da.gomez@samsung.com>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: I915-ci-infra@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, patchwork@emeril.freedesktop.org,
tools@kernel.org, d+samsung@kruces.com
Subject: Re: Incorrect response address when using B4
Date: Mon, 30 Sep 2024 17:45:08 +0300 [thread overview]
Message-ID: <87h69xw68b.fsf@intel.com> (raw)
In-Reply-To: <20240930143309.pwl7dzv537b2q3wk@AALNPWDAGOMEZ1.aal.scsc.local>
On Mon, 30 Sep 2024, Daniel Gomez <da.gomez@samsung.com> wrote:
> On Mon, Sep 30, 2024 at 10:20:57AM -0400, Konstantin Ryabitsev wrote:
>> On Mon, Sep 30, 2024 at 04:18:39PM GMT, Daniel Gomez wrote:
>> > > Was it an automated tool that sent you that message? Normally, email clients
>> > > would honour the "Reply-To" field and not use the From: address put in by the
>> > > relay.
>> >
>> > It was a CI Patchwork tool. Response [1] to my patch was sent from "From:
>> > Patchwork <patchwork@emeril.freedesktop.org>".
>> >
>> > [1] https://lore.kernel.org/all/172735727458.1107233.1757281470637305143@2413ebb6fbb6/
>> >
>> > I think that tool is ignoring the "Reply-To" field [2] from the B4 message and
>> > using the From field.
>> >
>> > From: Daniel Gomez via B4 Relay <devnull+da.gomez.samsung.com@kernel.org>
>> > Reply-To: da.gomez@samsung.com
>>
>> It's no big deal as long as you got the email response in the end. We expect
>> this to happen with a lot of automation, which is why any replies to the relay
>> address are auto-discarded.
>
> To clarify, the email response didn't land into my inbox. I realized a response
> was sent after checking at lore.kernel.org.
Yeah, our patchwork instance tries not to spam everyone, and limits the
replies to the submitter + intel-gfx/intel-xe mailing lists, but
apparently uses From instead of Reply-To.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-09-30 14:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240930133009eucas1p14b11ee712ae3ab1ca3aafc2833103bcb@eucas1p1.samsung.com>
2024-09-30 13:30 ` Incorrect response address when using B4 Daniel Gomez
2024-09-30 14:07 ` Konstantin Ryabitsev
2024-09-30 14:18 ` Daniel Gomez
2024-09-30 14:20 ` Konstantin Ryabitsev
2024-09-30 14:33 ` Daniel Gomez
2024-09-30 14:45 ` Jani Nikula [this message]
2024-09-30 21:15 ` Daniel Gomez
2024-10-01 8:26 ` Jani Nikula
2024-10-01 13:26 ` Konstantin Ryabitsev
2024-10-04 9:23 ` Daniel Gomez
2024-10-04 10:00 ` Jani Nikula
2024-09-30 14:09 ` Jani Nikula
2024-09-30 14:28 ` Daniel Gomez
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=87h69xw68b.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=I915-ci-infra@lists.freedesktop.org \
--cc=d+samsung@kruces.com \
--cc=da.gomez@samsung.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=konstantin@linuxfoundation.org \
--cc=patchwork@emeril.freedesktop.org \
--cc=tools@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.