From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-block@nongnu.org, qemu-stable@nongnu.org, jsnow@redhat.com,
Aarushi Mehta <mehta.aaru20@gmail.com>
Subject: [Qemu-devel] [PULL 1/3] docs/interop/bitmaps.rst: Fix typos
Date: Wed, 10 Jul 2019 15:23:04 -0400 [thread overview]
Message-ID: <20190710192306.28604-2-jsnow@redhat.com> (raw)
In-Reply-To: <20190710192306.28604-1-jsnow@redhat.com>
Pygments and Sphinx get pickier all the time; Sphinx 2.1+ now catches
these errors.
Signed-off-by: John Snow <jsnow@redhat.com>
Reported-by: Aarushi Mehta <mehta.aaru20@gmail.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Message-id: 20190603214653.29369-2-jsnow@redhat.com
Signed-off-by: John Snow <jsnow@redhat.com>
---
docs/interop/bitmaps.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/interop/bitmaps.rst b/docs/interop/bitmaps.rst
index 510e8809a9..c29ac4a854 100644
--- a/docs/interop/bitmaps.rst
+++ b/docs/interop/bitmaps.rst
@@ -399,7 +399,7 @@ in any one source bitmap, the target bitmap will mark that segment dirty.
"arguments": {
"node": "drive0",
"target": "new_bitmap",
- "bitmaps: [ "bitmap0" ]
+ "bitmaps": [ "bitmap0" ]
}
}
@@ -1437,7 +1437,7 @@ applied:
.. code:: json
<- {
- "timestamp": {...}
+ "timestamp": {...},
"data": {
"device": "drive0",
"type": "backup",
--
2.21.0
next prev parent reply other threads:[~2019-07-10 19:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 19:23 [Qemu-devel] [PULL 0/3] Bitmaps patches John Snow
2019-07-10 19:23 ` John Snow [this message]
2019-07-10 19:23 ` [Qemu-devel] [PULL 2/3] sphinx: add qmp_lexer John Snow
2019-07-10 19:23 ` [Qemu-devel] [PULL 3/3] docs/bitmaps: use QMP lexer instead of json John Snow
2019-07-11 11:30 ` [Qemu-devel] [PULL 0/3] Bitmaps patches Peter Maydell
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=20190710192306.28604-2-jsnow@redhat.com \
--to=jsnow@redhat.com \
--cc=mehta.aaru20@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=vsementsov@virtuozzo.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.