From: Ira Weiny <ira.weiny@intel.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
Dan Williams <dan.j.williams@intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Lukas Wunner <lukas@wunner.de>, <linux-pci@vger.kernel.org>,
<linux-acpi@vger.kernel.org>, Bjorn Helgaas <helgaas@kernel.org>
Subject: Re: [PATCH v4 0/9] CXL: Process event logs
Date: Mon, 12 Dec 2022 13:24:56 -0800 [thread overview]
Message-ID: <Y5ecKKUv+cz0s3N0@iweiny-desk3> (raw)
In-Reply-To: <20221212185459.x5wn42exhhycckun@meerkat.local>
On Mon, Dec 12, 2022 at 01:54:59PM -0500, Konstantin Ryabitsev wrote:
> On Mon, Dec 12, 2022 at 10:46:26AM -0800, Ira Weiny wrote:
> > > It fills out the To: and Cc: headers but doesn't actually send
> > > actual mail to those accounts. Mail servers don't actually pay any attention
> > > to those headers -- all that matters is what destinations are given to the
> > > server during the envelope negotiation.
> >
> > I did not know that. But I was kind of coming to that conclusion based on
> > what I saw happen.
> >
> > >
> > > I do realize that this is confusing. :/
> >
> > Only to those mere mortals such as myself who don't know squat about mail
> > protocols! :-D
>
> It's completely normal not to know how that works -- and you shouldn't either.
>
> > > Should I include anything in the output about this?
> >
> > Maybe. I'm not trying to put more burden on you. But for the ignorant maybe
> > it is a good idea. I did panic when I saw all the to/cc addresses filled in.
>
> I added a large notice about that to the --reflect output:
>
> [...]
> ---
> Ready to:
> - send the above messages to just konstantin@linuxfoundation.org (REFLECT MODE)
> - via web endpoint: https://lkml.kernel.org/_b4_submit
>
> REFLECT MODE:
> The To: and Cc: headers will be fully populated, but the only
> address given to the mail server for actual delivery will be
> konstantin@linuxfoundation.org
>
> Addresses in To: and Cc: headers will NOT receive this series.
>
> Press Enter to proceed or Ctrl-C to abort
>
> Hopefully, it will be less worrisome to others in the future.
Yes that should help a lot!
>
> Thank you for trying out b4 prep/send!
NP
Thanks!
Ira
next prev parent reply other threads:[~2022-12-12 21:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221211-test-b4-v4-0-9f45dfeec102@intel.com>
2022-12-12 5:32 ` [PATCH v4 0/9] CXL: Process event logs Ira Weiny
2022-12-12 16:16 ` Konstantin Ryabitsev
2022-12-12 18:46 ` Ira Weiny
2022-12-12 18:54 ` Konstantin Ryabitsev
2022-12-12 21:24 ` Ira Weiny [this message]
2022-12-12 7:06 [PATCH V4 " ira.weiny
2022-12-16 12:25 ` Jonathan Cameron
2022-12-16 17:01 ` Dan Williams
2022-12-16 18:15 ` Ira Weiny
2022-12-16 18:39 ` Jonathan Cameron
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=Y5ecKKUv+cz0s3N0@iweiny-desk3 \
--to=ira.weiny@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=helgaas@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
/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).