From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, John Snow <jsnow@redhat.com>
Cc: kwolf@redhat.com, famz@redhat.com, qemu-devel@nongnu.org,
Max Reitz <mreitz@redhat.com>,
vsementsov@parallels.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v11 03/13] qmp: Add block-dirty-bitmap-add and block-dirty-bitmap-remove
Date: Wed, 21 Jan 2015 08:51:43 -0700 [thread overview]
Message-ID: <54BFCB0F.2010002@redhat.com> (raw)
In-Reply-To: <878ugwpjdv.fsf@blackfin.pond.sub.org>
[-- Attachment #1: Type: text/plain, Size: 1406 bytes --]
On 01/21/2015 02:34 AM, Markus Armbruster wrote:
> Opinions?
>
I'm still thinking about my reply (it's a big enough question that I
want to make sure I consider ramifications), so this is just a
meta-reply to let you know I'm tracking this conversation.
>>>> CC'ing Eric Blake, as well, for comments on a "unified parameter"
>>>> interface in general.
>>>
>>> Good move.
>>>
>>>
>>> [*] https://lists.nongnu.org/archive/html/qemu-devel/2014-12/msg02572.html
>>>
>>
>> Adding Eric back in, where'd he go?
>
> Looks like you announced the cc:, but didn't actually do it, twice %-)
I know that on some lists I'm subscribed to, mailman has an annoying
configuration where if a list member is subscribed to the list and has
requested that mailman not send dupe emails, then mailman rewrites CC:
lines to drop that list member from the copy of the mail that other list
readers receive. I hate the behavior, but it may be why you appear to
not see me in cc, even though I've definitely been receiving the mails.
At any rate, I have my mail filters set to flag mails that call out my
name, even if I get left out from cc, so I can usually spot threads like
this where you are trying to get my attention, regardless of whether you
remembered to include me directly.
--
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-01-21 15:51 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 16:30 [Qemu-devel] [PATCH v11 00/13] block: Incremental backup series John Snow
2015-01-12 16:30 ` [Qemu-devel] [PATCH v11 01/13] block: fix spoiling all dirty bitmaps by mirror and migration John Snow
2015-01-13 15:54 ` Vladimir Sementsov-Ogievskiy
2015-01-12 16:30 ` [Qemu-devel] [PATCH v11 02/13] qapi: Add optional field "name" to block dirty bitmap John Snow
2015-01-12 16:30 ` [Qemu-devel] [PATCH v11 03/13] qmp: Add block-dirty-bitmap-add and block-dirty-bitmap-remove John Snow
2015-01-16 15:36 ` Max Reitz
2015-01-16 16:48 ` John Snow
2015-01-16 16:51 ` Max Reitz
2015-01-16 16:54 ` John Snow
2015-01-19 10:08 ` Markus Armbruster
2015-01-19 21:05 ` John Snow
2015-01-20 8:26 ` Markus Armbruster
2015-01-20 16:48 ` John Snow
2015-01-21 9:34 ` Markus Armbruster
2015-01-21 15:51 ` Eric Blake [this message]
2015-01-30 14:32 ` Kevin Wolf
2015-01-30 17:04 ` John Snow
2015-01-30 18:52 ` Kevin Wolf
2015-02-02 10:10 ` Markus Armbruster
2015-02-02 21:40 ` John Snow
2015-01-29 13:55 ` Vladimir Sementsov-Ogievskiy
2015-01-12 16:30 ` [Qemu-devel] [PATCH v11 04/13] block: Introduce bdrv_dirty_bitmap_granularity() John Snow
2015-01-16 15:40 ` Max Reitz
2015-01-12 16:30 ` [Qemu-devel] [PATCH v11 05/13] block: Add bdrv_clear_dirty_bitmap John Snow
2015-01-16 15:56 ` Max Reitz
2015-01-12 16:30 ` [Qemu-devel] [PATCH v11 06/13] hbitmap: add hbitmap_merge John Snow
2015-01-16 16:12 ` Max Reitz
2015-01-12 16:30 ` [Qemu-devel] [PATCH v11 07/13] qmp: Add block-dirty-bitmap-enable and block-dirty-bitmap-disable John Snow
2015-01-16 16:28 ` Max Reitz
2015-01-16 17:09 ` John Snow
2015-01-12 16:31 ` [Qemu-devel] [PATCH v11 08/13] block: Add bitmap successors John Snow
2015-01-13 9:24 ` Fam Zheng
2015-01-13 17:26 ` John Snow
2015-01-16 18:22 ` John Snow
2015-01-19 1:00 ` Fam Zheng
2015-01-12 16:31 ` [Qemu-devel] [PATCH v11 09/13] qmp: Add support of "dirty-bitmap" sync mode for drive-backup John Snow
2015-01-13 9:37 ` Fam Zheng
2015-01-13 17:50 ` John Snow
2015-01-14 6:29 ` Fam Zheng
2015-01-16 17:52 ` Max Reitz
2015-01-16 17:59 ` John Snow
2015-01-12 16:31 ` [Qemu-devel] [PATCH v11 10/13] qapi: Add transaction support to block-dirty-bitmap-{add, enable, disable} John Snow
2015-01-12 16:31 ` [Qemu-devel] [PATCH v11 11/13] qmp: Add dirty bitmap status fields in query-block John Snow
2015-01-12 16:31 ` [Qemu-devel] [PATCH v11 12/13] qemu-iotests: Add tests for drive-backup sync=dirty-bitmap John Snow
2015-02-06 14:23 ` Vladimir Sementsov-Ogievskiy
2015-02-06 17:14 ` John Snow
2015-01-12 16:31 ` [Qemu-devel] [PATCH v11 13/13] block: BdrvDirtyBitmap miscellaneous fixup John Snow
2015-01-13 16:50 ` Vladimir Sementsov-Ogievskiy
2015-01-13 18:27 ` John Snow
2015-01-13 1:21 ` [Qemu-devel] [PATCH v11 00/13] block: Incremental backup series Fam Zheng
2015-01-13 19:52 ` John Snow
2015-01-29 22:38 ` John Snow
2015-01-30 10:24 ` Vladimir Sementsov-Ogievskiy
2015-01-30 18:46 ` John Snow
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=54BFCB0F.2010002@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@parallels.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).