From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
qemu block <qemu-block@nongnu.org>, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v2 0/2] block: driver should override flags in bdrv_open()
Date: Tue, 09 Jun 2015 09:21:50 -0600 [thread overview]
Message-ID: <5577048E.6050304@redhat.com> (raw)
In-Reply-To: <CAJSP0QV_0wGU_+31Ex8TrgJZbAZhaRxY5+aE-i9vWrHEneRrWQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1355 bytes --]
On 06/09/2015 08:48 AM, Stefan Hajnoczi wrote:
> I guess my @redhat.com email was received directly from Max because I
> was in CC list. It didn't pass through Mailman. I saw the original,
> unmodified list of CCs with Kevin included.
>
> The @gmail.com email was received from the mailing list. Mailman did
> what you described.
And that's what makes it so annoying. Original recipients have the full
list, but later additions to the thread don't know who the original
recipients were, only that including the list in reply will also reach
the original recipients (albeit maybe not filtered into the right folder).
I have no idea if mailman has some tweakable setting that can change
this bad out-of-the-box default of munging cc's that so many lists use,
but even if it does, it requires a list admin to tweak the setting, for
each affected list.
>
> This means I cannot send "Please CC maintainer" emails anymore because
> I cannot be sure whether the maintainer was CCed!
Well, unless you know the maintainer is one of the people who does NOT
use the mailman setting of "don't send me duplicate mails" (sadly, we
have deduced that Kevin does use it, making it harder to tell if he is
aware of a thread).
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-06-09 16:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 18:53 [Qemu-devel] [PATCH v2 0/2] block: driver should override flags in bdrv_open() Max Reitz
2015-03-19 18:53 ` [Qemu-devel] [PATCH v2 1/2] " Max Reitz
2015-03-19 18:53 ` [Qemu-devel] [PATCH v2 2/2] iotests: Add tests for overriding BDRV_O_PROTOCOL Max Reitz
2015-04-24 14:37 ` [Qemu-devel] [PATCH v2 0/2] block: driver should override flags in bdrv_open() Max Reitz
2015-06-03 19:49 ` Max Reitz
2015-06-09 8:41 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2015-06-09 8:59 ` Kevin Wolf
2015-06-09 10:19 ` Stefan Hajnoczi
2015-06-09 11:36 ` Kevin Wolf
2015-06-09 11:49 ` Eric Blake
2015-06-09 14:48 ` Stefan Hajnoczi
2015-06-09 15:21 ` Eric Blake [this message]
2015-06-10 8:37 ` Kevin Wolf
2015-06-11 8:27 ` Stefan Hajnoczi
2015-06-12 14:36 ` [Qemu-devel] " Kevin Wolf
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=5577048E.6050304@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@redhat.com \
/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).