From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Gomez <da.gomez@samsung.com>, I915-ci-infra@lists.freedesktop.org
Cc: 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:09:54 +0300 [thread overview]
Message-ID: <87msjpw7v1.fsf@intel.com> (raw)
In-Reply-To: <20240930133007.u4vm5qj5urikpmvc@AALNPWDAGOMEZ1.aal.scsc.local>
On Mon, 30 Sep 2024, Daniel Gomez <da.gomez@samsung.com> wrote:
> Hi,
>
> I sent this patch [1] using B4 web endpoint and then I received a
> response email to the wrong address: To: "Daniel Gomez via B4 Relay"
> <devnull+da.gomez.samsung.com@kernel.org> instead of To: "Daniel Gomez"
> <da.gomez@samsung.com>.
>
> [1] https://lore.kernel.org/all/20240925-macos-build-support-v3-1-233dda880e60@samsung.com/
I guess you're saying the replies should be using the Reply-To: header.
Oddly enough, even my MUA doesn't respect the Reply-To: header when the
same address is already in To:/Cc:, as a way to handle mailing list
Reply-To "munging" [1].
BR,
Jani.
[1] http://marc.merlins.org/netrants/reply-to-harmful.html
>
> Is this something that can be fixed on the CI, patchwork side?
>
> Thanks,
> Daniel
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-09-30 14:10 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
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 [this message]
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=87msjpw7v1.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=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 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).