From: Kashyap Chamarthy <kchamart@redhat.com>
To: qemu-devel@nongnu.org
Cc: eblake@redhat.com, qemu-block@nongnu.org, kwolf@redhat.com,
mreitz@redhat.com, jsnow@redhat.com, berto@igalia.com,
Kashyap Chamarthy <kchamart@redhat.com>
Subject: [Qemu-devel] [PATCH v5 0/2] Rewrite 'live-block-ops.txt'; convert 'bitmaps.md' to rST
Date: Thu, 6 Jul 2017 16:36:44 +0200 [thread overview]
Message-ID: <1499351806-3359-1-git-send-email-kchamart@redhat.com> (raw)
[v4: https://lists.nongnu.org/archive/html/qemu-devel/2017-06/msg06395.html]
Rewrite the 'live-block-ops.txt' document (after renaming it to
'live-block-operations.rst') in reStructuredText (rST) format. Given
upstream QEMU's desire[*] to take advantage of the Sphinx + rST
framework to gerate its documentation:
"Based on experience from the Linux kernel, QEMU's docs pipeline is
going to be based on Sphinx [...] Sphinx is extensible and it is
easy to add new input formats and input directives."
And as part of review, John Snow suggested[+] to link to the
'bitmaps.md' document. So while at it, convert the 'bitmaps.md'
document also into rST syntax.
Then, moved both the documents ('live-block-operations.rst', and
'bitmaps.rst') to 'qemu/docs/interop' directory. (Paolo explained the
term "interop" as: "management & interoperability with QEMU".)
That's the result of this series:
(1) Rewrite the 'live-block-ops.txt' document (for details, refer the
commit message of the patch) in rST.
Sphinx-generted HTML rendering:
https://kashyapc.fedorapeople.org/v5-QEMU-Docs/_build/html/docs/live-block-operations.html
(2) Convert the 'bitmaps.md' document to rST, as discussed on this[+]
thread.
Sphinx-generted HTML rendering:
https://kashyapc.fedorapeople.org/v5-QEMU-Docs/_build/html/docs/bitmaps.html
[*] http://wiki.qemu.org/Features/Documentation
[+] https://lists.nongnu.org/archive/html/qemu-devel/2017-06/msg05428.html
Kashyap Chamarthy (2):
bitmaps.md: Convert to rST; move it into 'interop' dir
live-block-ops.txt: Rename, rewrite, and improve it
docs/devel/bitmaps.md | 505 ---------------
docs/interop/bitmaps.rst | 555 +++++++++++++++++
docs/interop/live-block-operations.rst | 1072 ++++++++++++++++++++++++++++++++
docs/live-block-ops.txt | 72 ---
4 files changed, 1627 insertions(+), 577 deletions(-)
delete mode 100644 docs/devel/bitmaps.md
create mode 100644 docs/interop/bitmaps.rst
create mode 100644 docs/interop/live-block-operations.rst
delete mode 100644 docs/live-block-ops.txt
--
2.7.5
next reply other threads:[~2017-07-06 14:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 14:36 Kashyap Chamarthy [this message]
2017-07-06 14:36 ` [Qemu-devel] [PATCH v5 1/2] bitmaps.md: Convert to rST; move it into 'interop' dir Kashyap Chamarthy
2017-07-06 14:36 ` [Qemu-devel] [PATCH v5 2/2] live-block-ops.txt: Rename, rewrite, and improve it Kashyap Chamarthy
2017-07-06 18:11 ` Kashyap Chamarthy
2017-07-06 22:41 ` John Snow
2017-07-07 10:46 ` Kashyap Chamarthy
2017-07-07 21:08 ` John Snow
2017-07-07 22:25 ` John Snow
2017-07-10 7:53 ` Kashyap Chamarthy
2017-07-10 16:23 ` 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=1499351806-3359-1-git-send-email-kchamart@redhat.com \
--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).