From: Kashyap Chamarthy <kchamart@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, kwolf@redhat.com,
mreitz@redhat.com, jsnow@redhat.com, berto@igalia.com
Subject: Re: [Qemu-devel] [PATCH v6 1/2] bitmaps.md: Convert to rST; move it into 'interop' dir
Date: Tue, 11 Jul 2017 09:58:39 +0200 [thread overview]
Message-ID: <20170711075839.wgp64avrkzyo6d6t@eukaryote> (raw)
In-Reply-To: <251c3898-8d5f-a799-318e-5ab0545220a3@redhat.com>
On Mon, Jul 10, 2017 at 09:36:50PM -0500, Eric Blake wrote:
> On 07/10/2017 03:15 AM, Kashyap Chamarthy wrote:
[...]
> > Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
> > Reviewed-by: John Snow <jsnow@redhat.com>
> > ---
>
> > ---
> > docs/devel/bitmaps.md | 505 ------------------------------------------
> > docs/interop/bitmaps.rst | 555 +++++++++++++++++++++++++++++++++++++++++++++++
>
> A shame that git rename detection doesn't see these as the same rough
> contents, but not too bad.
_Should_ it detect?
> I'll just review the new text; if I point out
> something that was pre-existing in the old text, it may be nicer to
> split the cleanups into a separate followup patch, but I'm also okay if
> they go in as part of this patch.
Indeed -- the things you point out further below were already
pre-existing.
Asking out of curiosity: You say it is nicer split because we'll retain
the `git-bisect`-ability? Or just to keep text motion and actual
changes separate? (I think both.)
> My review is less focused on the choices used in representing things in
> rST and on the final display outcome, and more on the text itself
> (grammar and such).
Noted.
>
> > +++ b/docs/interop/bitmaps.rst
> > +
> > +- Dirty bitmaps can be created at any time and attached to any node
> > + (not just complete drives.)
>
> Looks a bit nicer with '.' outside the sub-sentence '()'.
Will fix.
> > +
> > +.. contents::
> > +
> > +Dirty Bitmap Names
> > +------------------
> > +
> > +- A dirty bitmap's name is unique to the node, but bitmaps attached to
> > + different nodes can share the same name.
> > +
> > +- Dirty bitmaps created for internal use by QEMU may be anonymous and
> > + have no name, but any user-created bitmaps may not be. There can be
>
> s/may not be/must have a name/
Will fix.
>
> > +
> > +- This bitmap will have a default granularity that matches the cluster
> > + size of its associated drive, if available, clamped to between [4KiB,
>
> s/clamped to/clamped/
Will fix.
> > + 64KiB]. The current default for qcow2 is 64KiB.
> > +
> > +
>
>
> > +- QMP example response, highlighting one success and one failure:
> > +
> > + - Acknowledgement that the Transaction was accepted and jobs were
> > + launched:
>
> US spelling prefers Acknowledgment, but I think you are okay because of
> UK spelling.
It was John Snow who wrote this document. :-)
I realize that you merely pointed out the difference. And the QEMU
upstream documentation also says they accept both US and UK spellings:
http://wiki.qemu.org/Contribute/SpellCheck
> Again, since these are probably pre-existing and just code motion, and
> if you've gotten positive review of your use of rST, I'm fine with adding:
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
Thank you.
I'll wait for feedback on the other (much longer and completely
overhauled) document -- if there's a need to respin it, I'll address
your feedback from here.
[...]
--
/kashyap
next prev parent reply other threads:[~2017-07-11 7:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 8:15 [Qemu-devel] [PATCH v6 0/2] Rewrite 'live-block-ops.txt'; convert 'bitmaps.md' to rST Kashyap Chamarthy
2017-07-10 8:15 ` [Qemu-devel] [PATCH v6 1/2] bitmaps.md: Convert to rST; move it into 'interop' dir Kashyap Chamarthy
2017-07-11 2:36 ` Eric Blake
2017-07-11 7:58 ` Kashyap Chamarthy [this message]
2017-07-11 11:33 ` Eric Blake
2017-07-11 11:49 ` Kashyap Chamarthy
2017-07-11 16:11 ` John Snow
2017-07-10 8:15 ` [Qemu-devel] [PATCH v6 2/2] live-block-ops.txt: Rename, rewrite, and improve it Kashyap Chamarthy
2017-07-11 15:03 ` Eric Blake
2017-07-17 9:14 ` Kashyap Chamarthy
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=20170711075839.wgp64avrkzyo6d6t@eukaryote \
--to=kchamart@redhat.com \
--cc=berto@igalia.com \
--cc=eblake@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@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).