From: John Snow <jsnow@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Fam Zheng <fam@euphon.net>,
Aarushi Mehta <mehta.aaru20@gmail.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org,
Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] Add QMP lexer for annotated JSON to Sphinx
Date: Mon, 3 Jun 2019 14:04:24 -0400 [thread overview]
Message-ID: <4216a20b-1b23-e1cd-3479-1d1011e9d683@redhat.com> (raw)
In-Reply-To: <20190523121230.17193-1-jsnow@redhat.com>
Peter: I think this one would be through your tree if anyone's, yes? Any
thoughts?
--js
On 5/23/19 8:12 AM, John Snow wrote:
> QMP isn't json. It turns out Pygments cares about this.
> Teach Pygments to go with the annotated flow.
>
> V2:
> - Change GPL2 to GPLv2+ (Peter Maydell)
> - Change "highlights" to "lexes" in docstrings
> - Fix typo ("Sphinx()" => "Sphinx") in docstring
>
> Reported-by: Aarushi Mehta <mehta.aaru20@gmail.com>
>
> John Snow (2):
> sphinx: add qmp_lexer
> docs/bitmaps: use QMP lexer instead of json
>
> docs/conf.py | 4 +--
> docs/interop/bitmaps.rst | 54 ++++++++++++++++++++--------------------
> docs/sphinx/qmp_lexer.py | 34 +++++++++++++++++++++++++
> 3 files changed, 63 insertions(+), 29 deletions(-)
> create mode 100644 docs/sphinx/qmp_lexer.py
>
prev parent reply other threads:[~2019-06-03 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 12:12 [Qemu-devel] [PATCH v2 0/2] Add QMP lexer for annotated JSON to Sphinx John Snow
2019-05-23 12:12 ` [Qemu-devel] [PATCH v2 1/2] sphinx: add qmp_lexer John Snow
2019-05-23 12:12 ` [Qemu-devel] [PATCH v2 2/2] docs/bitmaps: use QMP lexer instead of json John Snow
2019-06-03 18:04 ` John Snow [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=4216a20b-1b23-e1cd-3479-1d1011e9d683@redhat.com \
--to=jsnow@redhat.com \
--cc=ehabkost@redhat.com \
--cc=fam@euphon.net \
--cc=mehta.aaru20@gmail.com \
--cc=peter.maydell@linaro.org \
--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).