From: "David Woodhouse" <dwmw2@infradead.org>
To: devel@edk2.groups.io, lersek@redhat.com
Subject: Re: [edk2-devel] [PATCH v3 0/4] OvmfPkg: CSM boot fixes
Date: Wed, 26 Jun 2019 13:41:11 +0100 [thread overview]
Message-ID: <d1803b3fc8a1618448dc384a8b2215f2c0c15808.camel@infradead.org> (raw)
In-Reply-To: <3e5e44e2c2714ddf0aeb604023ae6ad07b789583.camel@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]
On Wed, 2019-06-26 at 13:33 +0100, David Woodhouse wrote:
>
> Wow, this is just completely brain-damaged on so many levels. So people
> who do, and who don't, have that box checked will receive the same
> message with *different* Message-Id: headers?
>
> If one of them replies, the In-Reply-To: threading header in their
> reply will refer to a message that *doesn't* exist in the other
> person's mailbox. This kind of explains why threading was so broken for
> messages on the list, with some response getting 'lost' because they
> were detached from the thread. This does not facilitate effective
> communication.
>
> Did nobody at groups.io ever stop and think this through? Can it really
> not be turned off for the whole list? Why on earth did we move the list
> to somewhere that can't even get the *basics* right?
Ah, so it's not *quite* as broken as that, because it does only mangle
a user's *own* messages back to them; not all messages to them.
So threading works a bit.... except for threads you *participate* in.
Yay!
But at least opting out can mostly isolate an individual from the
adverse effects of this strangeness, and it isn't inflicted upon us
(much) by others who haven't opted out.
> Should I offer to set one up @lists.infradead.org?
Offer still stands :)
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5174 bytes --]
next prev parent reply other threads:[~2019-06-26 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15ABBC9A305FBCEC.16820@groups.io>
2019-06-26 11:43 ` [edk2-devel] [PATCH v3 0/4] OvmfPkg: CSM boot fixes David Woodhouse
2019-06-26 12:18 ` Laszlo Ersek
2019-06-26 12:33 ` David Woodhouse
2019-06-26 12:41 ` David Woodhouse [this message]
2019-06-26 14:48 ` Laszlo Ersek
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-list 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=d1803b3fc8a1618448dc384a8b2215f2c0c15808.camel@infradead.org \
--to=devel@edk2.groups.io \
/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