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: Fri, 04 Oct 2024 13:00:24 +0300 [thread overview]
Message-ID: <87bk00rxvr.fsf@intel.com> (raw)
In-Reply-To: <D4MWUZ2F8B75.2LOQZKGUBIBWK@samsung.com>
On Fri, 04 Oct 2024, Daniel Gomez <da.gomez@samsung.com> wrote:
> On Mon Sep 30, 2024 at 4:20 PM CEST, 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.
>
> Konstantin,
>
> B4 web endpoint works very well for me because of the freedom it gives me for
> sending patches. However, as a user of this feature I'm expecting all replies
> to go into my inbox (regardless of whether it is an automated respose or
> not). Unfortunately, they don't. So, what I'm asking here is if it would be
> possible for these automated responses from Intel 0-day, Intel GFX CI (Patchwork
> Freedesktop) and lore (public inbox), to change their responses to use the
> "Reply-To" field instead of "From". Note that the first 2, completely remove all
> the Cc addresses. IIUC and according to the Jani's answer, this seems to be not
> doable on their end. I'm not sure about lore's side.
I think the request is reasonable, and I sure didn't mean to give the
impression that it's not doable.
But it's still three distinct projects with their own developers that
need to be convinced to make the change. (And if it's not clear I'm not
one of those developers.)
> Is it posible to change the "Reply instructions" section in lore, to use the
> "Reply-To" field? It won't solve the problem completely but at least users of
> that would use the right git-send-email command.
>
> Also, what's the use case of using B4 web endpoint if replies may or may not
> land in the sender's inbox? I think the use of this feature requires proactively
> monitoring the patch and/or mailing list.
In most cases you'd expect people to "reply all", and if you have your
address in Cc:, you're covered. Lore's instructions do that. It's the
cases that limit recipients to reduce what might be consider spam that
have the issue.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-10-04 10:00 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 [this message]
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=87bk00rxvr.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 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).