From: Thomas Huth <thuth@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>, qemu-devel@nongnu.org
Cc: Laurent Vivier <lvivier@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 0/3] docs: Include QTest protocol and libqtest API on documentation
Date: Tue, 6 Oct 2020 19:12:53 +0200 [thread overview]
Message-ID: <64fc2c1a-0751-6b6a-1499-9dae8c7ea100@redhat.com> (raw)
In-Reply-To: <20201005205228.697463-1-ehabkost@redhat.com>
On 05/10/2020 22.52, Eduardo Habkost wrote:
> This moves the QTest section of testing.rst to a separate
> document, and include the QTest Protocol specification and
> libqtest API reference in the document.
>
> Eduardo Habkost (3):
> docs: Move QTest documentation to its own document
> docs/devel/qtest: Include protocol spec in document
> docs/devel/qtest: Include libqtest API reference
>
> docs/devel/index.rst | 1 +
> docs/devel/qtest.rst | 72 ++++++++++++++++++++++++++++++++++
> docs/devel/testing.rst | 47 +---------------------
> tests/qtest/libqos/libqtest.h | 20 +++++-----
> softmmu/qtest.c | 73 +++++++++++++++++++++++++++++++----
> 5 files changed, 150 insertions(+), 63 deletions(-)
> create mode 100644 docs/devel/qtest.rst
FWIW:
Acked-by: Thomas Huth <thuth@redhat.com>
prev parent reply other threads:[~2020-10-06 17:13 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
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 [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=64fc2c1a-0751-6b6a-1499-9dae8c7ea100@redhat.com \
--to=thuth@redhat.com \
--cc=ehabkost@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--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).