From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>, qemu-devel@nongnu.org
Cc: Laurent Vivier <lvivier@redhat.com>, Thomas Huth <thuth@redhat.com>
Subject: Re: [PATCH 2/3] docs/devel/qtest: Include protocol spec in document
Date: Wed, 7 Oct 2020 13:03:21 +0200 [thread overview]
Message-ID: <27b0312b-cef9-9aea-3196-871eeca6760d@redhat.com> (raw)
In-Reply-To: <20201005205228.697463-3-ehabkost@redhat.com>
On 05/10/20 22:52, Eduardo Habkost wrote:
> + * DOC: QTest Protocol
> + *
> + * .. highlight:: none
> *
> * Line based protocol, request/response based. Server can send async messages
> * so clients should always handle many async messages before the response
> * comes in.
> *
> * Valid requests
> + * ^^^^^^^^^^^^^^
> *
> * Clock management:
> + * """""""""""""""""
> *
> * The qtest client is completely in charge of the QEMU_CLOCK_VIRTUAL. qtest commands
> * let you adjust the value of the clock (monotonically). All the commands
> * return the current value of the clock in nanoseconds.
> *
> + * .. code-block::
What version of Sphinx do you have? I need to have ".. code-block::
none" here, so presumably the "highlight" directive is newer than my
version (1.7.6, pretty old I admit)?
Paolo
next prev parent reply other threads:[~2020-10-07 11:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 20:52 [PATCH 0/3] docs: Include QTest protocol and libqtest API on documentation Eduardo Habkost
2020-10-05 20:52 ` [PATCH 1/3] docs: Move QTest documentation to its own document Eduardo Habkost
2020-10-05 20:52 ` [PATCH 2/3] docs/devel/qtest: Include protocol spec in document Eduardo Habkost
2020-10-07 11:03 ` Paolo Bonzini [this message]
2020-10-07 11:39 ` Eduardo Habkost
2020-10-07 12:01 ` Paolo Bonzini
2020-10-05 20:52 ` [PATCH 3/3] docs/devel/qtest: Include libqtest API reference Eduardo Habkost
2020-10-06 17:12 ` Thomas Huth
2020-10-06 17:22 ` Eduardo Habkost
2020-10-06 12:42 ` [PATCH 0/3] docs: Include QTest protocol and libqtest API on documentation Paolo Bonzini
2020-10-06 17:12 ` Thomas Huth
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=27b0312b-cef9-9aea-3196-871eeca6760d@redhat.com \
--to=pbonzini@redhat.com \
--cc=ehabkost@redhat.com \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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 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).