From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>, Kevin Wolf <kwolf@redhat.com>
Cc: 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 05:49:40 -0600 [thread overview]
Message-ID: <5576D2D4.9050106@redhat.com> (raw)
In-Reply-To: <20150609101958.GA27900@stefanha-thinkpad.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1754 bytes --]
On 06/09/2015 04:19 AM, Stefan Hajnoczi wrote:
> On Tue, Jun 09, 2015 at 10:59:42AM +0200, Kevin Wolf wrote:
>> Am 09.06.2015 um 10:41 hat Stefan Hajnoczi geschrieben:
>>> On Thu, Mar 19, 2015 at 6:53 PM, Max Reitz <mreitz@redhat.com> wrote:
>>>> BDRV_O_PROTOCOL is an internal qemu flag which a user should be able to
>>>> override by explicitly specifying a block driver. This series implements
>>>> this and adds two iotests (one for NBD, one for file) to test it.
>>>>
>>> Please resend and CC Kevin (for qemu-iotests and block.c).
>>
>> It's only you who dropped me from CC. :-)
>
> For sanity, can you check whether you are on the CC list in Max's second
> ping message: 556F5A4D.50903@redhat.com?
>
> I had another CC mix-up recently and want to check whether my mail tools
> are dropping CCs or if it's just me being confused.
mailman has an (extremely annoying, in my opinion) habit of munging cc:
lines to drop the name of any recipient who has set their list delivery
options to avoid duplicate messages where the recipient is in cc.
Ultimately, the end user still gets the messages (reply-to-all gets the
message back to the list, even though it drops the cc), but at the
expense of not directly going to the inbox as desired. At least I still
only get one copy of the message, but yes, I'd rather have that one copy
come directly to me for all messages in the thread, rather than through
the list because I was munged out of cc.
I hope that mailman3/hyperkitty will have saner defaults and not munge
cc lists to exclude subscribers merely based on their preference on
duplicate mail receipt.
--
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 11:49 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 [this message]
2015-06-09 14:48 ` Stefan Hajnoczi
2015-06-09 15:21 ` Eric Blake
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=5576D2D4.9050106@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).