All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Vaibhav Bhembre <vaibhav@digitalocean.com>
Cc: qemu-devel@nongnu.org, Josh Durgin <jdurgin@redhat.com>,
	Jeff Cody <jcody@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
	Max Reitz <mreitz@redhat.com>,
	Luiz Capitulino <lcapitulino@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	qemu block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2] rbd: reload ceph config for block device
Date: Thu, 14 Jul 2016 15:19:38 -0600	[thread overview]
Message-ID: <578801EA.3020505@redhat.com> (raw)
In-Reply-To: <CADJota_dFaNEkmWsrSXJmfRpXPSFzz0yXvLgNXCu5=CJqR6WwA@mail.gmail.com>

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

On 07/14/2016 02:53 PM, Vaibhav Bhembre wrote:
> Thanks Eric!

meta-comment - your mailer's default quoting behavior makes it very hard
to read your replies.  Observe:

> 
> On Thu, Jul 14, 2016 at 4:28 PM, Eric Blake <eblake@redhat.com> wrote:
> 
>> On 07/14/2016 01:32 PM, Vaibhav Bhembre wrote:
>>> This patch adds ability to reload ceph configuration for an attached RBD
>>> block device. This is necessary for the cases where rebooting a VM and/or
>>> detaching-reattaching a RBD drive is not an easy option.
>>
>> Probably worth including qemu-block@nongnu.org if you resend this. I've
>> added them in cc now, per the output of:
>>  scripts/get_maintainer.pl -f block/rbd
>>
>>>
>>> The reload mechanism relies on the bdrv_reopen_* calls to provide a
>> transactional
>>> guarantee (using 2PC) for pulling in new configuration parameters. In
>> the _prepare

Your mailer wrapped your lines but used inconsistent prefix when doing
so, which makes attribution of the lines difficult (some start with
'>>>', which traces to you, some start with '>>' which traces to me) (of
course, this is after my mailer has added yet another round of >
prefixing, but at least I know my mailer [Thunderbird] has sane quoting
behavior for the most part).

...
>>> +# Since: 2.7
>>
>> v1 was posted June 17, before soft freeze on June 28, so this may still
>> make hard freeze if someone picks it up before hard freeze on July 19.
>> But we're getting close.
>>
>> ​Hoping so! ​
> 

Here, both my text ("But we're getting close") and your text ("Hoping
so!") are prefixed with the same '>>' prefix, which makes it sound like
I wrote your reply.


>> We may want to rebase this on top of Kevin's series that adds
>> qmp_get_root_bs()
>> https://lists.gnu.org/archive/html/qemu-devel/2016-07/msg03086.html
>>
>> ​This is exactly what I need. Should I wait for other reviews before
> making this change or should I push it right-away?

and here, half your paragraph is attributed to me (prefix of '>>') while
only the second half is attributed to you (prefix of '>').

-- 
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 --]

  reply	other threads:[~2016-07-14 21:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-14 19:32 [Qemu-devel] [PATCH v2] rbd: reload ceph config for block device Vaibhav Bhembre
2016-07-14 20:28 ` Eric Blake
2016-07-14 20:53   ` Vaibhav Bhembre
2016-07-14 21:19     ` Eric Blake [this message]
2016-07-14 23:14       ` Vaibhav Bhembre

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=578801EA.3020505@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=jcody@redhat.com \
    --cc=jdurgin@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vaibhav@digitalocean.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.