From: Kashyap Chamarthy <kchamart@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, mreitz@redhat.com,
armbru@redhat.com, jsnow@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 for-2.11] QAPI & interop: Clarify events emitted by 'block-job-cancel'
Date: Fri, 17 Nov 2017 18:26:54 +0100 [thread overview]
Message-ID: <20171117172654.ucimuik2ixcu2qfw@eukaryote> (raw)
In-Reply-To: <78f4339b-bbe5-18d1-6555-b2c3196a6f7c@redhat.com>
On Fri, Nov 17, 2017 at 11:07:41AM -0600, Eric Blake wrote:
> On 11/17/2017 10:25 AM, Kashyap Chamarthy wrote:
[...]
> Sorry for not wordsmithing on earlier versions:
That's fine. Always appreciate your wordsmithing :-)
> > + 'mirror' job *after* it has indicated (by emitting the event
> > + ``BLOCK_JOB_READY``) that the source and target now remain
> > + synchronized, then ``block-job-cancel`` will emit the event
>
> Might read slightly nicer as:
>
> the source and target have reached synchronization,
Ah, that sounds nicer indeed. Will fix.
[...]
> > +# Note that the 'block-job-cancel' command will emit the event
> > +# BLOCK_JOB_COMPLETED if you issue it ('block-job-cancel') after 'drive-mirror'
> > +# has indicated (by emitting the event BLOCK_JOB_READY) that the source and
> > +# destination remain synchronized. In this case, the BLOCK_JOB_COMPLETED
> > +# event indicates that synchronization (from 'drive-mirror') has successfully
> > +# ended and the destination now has a point-in-time copy, which is at the time
> > +# of cancel.
>
>
> Accurate, but a bit hard to follow the flow of the sentence.
Yeah, I wasn't satisfied with my phrasing too. I sat on it for nearly
half an hour, and still it came out super clunky.
> Might read nicer as:
>
> Note that if you issue 'block-job-cancel' after 'drive-mirror' has
> indicated (via the event BLOCK_JOB_READY) that the source and
> destination are synchronized, then the event triggered by this command
> changes to BLOCK_JOB_COMPLETED, to indicate that the mirroring has
> ended and the destination now has a point-in-time copy tied to the
> time of the cancellation.
Thanks, yours reads much nicer.
> Documentation is worth of inclusion in 2.11. Whether you keep your
> wording, or incorporate mine in a v4, you can add:
> Reviewed-by: Eric Blake <eblake@redhat.com>
I'll definitely incorporate in v4.
I'll also make similar wording adjustment in live-block-operations.rst.
Thanks for the quick review.
--
/kashyap
prev parent reply other threads:[~2017-11-17 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 16:25 [Qemu-devel] [PATCH v3] QAPI & interop: Clarify events emitted by 'block-job-cancel' Kashyap Chamarthy
2017-11-17 17:07 ` [Qemu-devel] [PATCH v3 for-2.11] " Eric Blake
2017-11-17 17:26 ` Kashyap Chamarthy [this message]
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=20171117172654.ucimuik2ixcu2qfw@eukaryote \
--to=kchamart@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=jsnow@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).