public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
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:33:12 +0100	[thread overview]
Message-ID: <3e5e44e2c2714ddf0aeb604023ae6ad07b789583.camel@infradead.org> (raw)
In-Reply-To: <b9e78615-0603-9676-8960-700fb63797e3@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1632 bytes --]

On Wed, 2019-06-26 at 14:18 +0200, Laszlo Ersek wrote:
> 
> Yes, it can be turned off. It is a common hiccup for new subscribers
> (the groups.io default is broken). I think we meant to document it
> somewhere (outside of the mailing list archive), and I guess we may have
> even done so, but currently a non-list reference escapes me.
> 
> Anyway, please see the attached messages -- and then please log in to
> your groups.io account, locate
> 
>   Account
>     Preferences
>       Email Preferences
>         My Posts
>           I always want copies of my own emails
> 
> and *uncheck* it.

Thanks.

> Because, in reality, that checkbox stands for "munge my Message-IDs so
> that GMail doesn't de-duplicate my own emails when the list reflects
> them to me". But, two wrongs don't make a right :/

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?

Should I offer to set one up @lists.infradead.org?

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5174 bytes --]

  reply	other threads:[~2019-06-26 12:33 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 [this message]
2019-06-26 12:41       ` David Woodhouse
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=3e5e44e2c2714ddf0aeb604023ae6ad07b789583.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