From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 12/12] docs: Belatedly update for move of QMP/* to docs/
Date: Fri, 7 Oct 2016 14:09:19 +0200 [thread overview]
Message-ID: <1475842159-26039-13-git-send-email-armbru@redhat.com> (raw)
In-Reply-To: <1475842159-26039-1-git-send-email-armbru@redhat.com>
Missed in commit 7537fe0 and commit 9b89b6a.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <1475766600-7273-1-git-send-email-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
---
docs/qmp-commands.txt | 2 +-
docs/writing-qmp-commands.txt | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/qmp-commands.txt b/docs/qmp-commands.txt
index e0adceb..b289391 100644
--- a/docs/qmp-commands.txt
+++ b/docs/qmp-commands.txt
@@ -20,7 +20,7 @@ Also, the following notation is used to denote data flow:
-> data issued by the Client
<- Server data response
-Please, refer to the QMP specification (QMP/qmp-spec.txt) for detailed
+Please, refer to the QMP specification (docs/qmp-spec.txt) for detailed
information on the Server command and response formats.
NOTE: This document is temporary and will be replaced soon.
diff --git a/docs/writing-qmp-commands.txt b/docs/writing-qmp-commands.txt
index cfa6fe7..44c14db 100644
--- a/docs/writing-qmp-commands.txt
+++ b/docs/writing-qmp-commands.txt
@@ -7,8 +7,8 @@ This document doesn't discuss QMP protocol level details, nor does it dive
into the QAPI framework implementation.
For an in-depth introduction to the QAPI framework, please refer to
-docs/qapi-code-gen.txt. For documentation about the QMP protocol, please
-check the files in QMP/.
+docs/qapi-code-gen.txt. For documentation about the QMP protocol,
+start with docs/qmp-intro.txt.
== Overview ==
--
2.5.5
next prev parent reply other threads:[~2016-10-07 12:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 12:09 [Qemu-devel] [PULL 00/12] QAPI patches for 2016-10-07 Markus Armbruster
2016-10-07 12:09 ` [Qemu-devel] [PULL 01/12] qmp: fix object-add assert() without props Markus Armbruster
2016-10-07 12:09 ` [Qemu-devel] [PULL 02/12] qapi: Fix crash when 'any' or 'null' parameter is missing Markus Armbruster
2016-10-07 12:09 ` [Qemu-devel] [PULL 03/12] tests/test-qmp-input-strict: Cover missing struct members Markus Armbruster
2016-10-07 12:09 ` [Qemu-devel] [PULL 04/12] tests: start generic qemu-qmp tests Markus Armbruster
2016-10-07 12:09 ` [Qemu-devel] [PULL 05/12] qapi: add assert about root value Markus Armbruster
2016-10-07 12:09 ` [Qemu-devel] [PULL 06/12] qapi: assert list entry has a value Markus Armbruster
2016-10-07 12:09 ` [Qemu-devel] [PULL 07/12] qapi: return a 'missing parameter' error Markus Armbruster
2016-10-07 12:09 ` [Qemu-devel] [PULL 08/12] MAINTAINERS: Pass the HMP staff from Luiz to David Markus Armbruster
2016-10-07 12:09 ` [Qemu-devel] [PULL 09/12] MAINTAINERS: Pass the QObject staff from Luiz to Markus Markus Armbruster
2016-10-07 12:09 ` [Qemu-devel] [PULL 10/12] qmp: Disable query-cpu-* commands when they're unavailable Markus Armbruster
2016-10-07 12:09 ` [Qemu-devel] [PULL 11/12] docs: Belatedly update for move of qmp-commands.txt Markus Armbruster
2016-10-07 12:09 ` Markus Armbruster [this message]
2016-10-07 14:14 ` [Qemu-devel] [PULL 00/12] QAPI patches for 2016-10-07 Peter Maydell
2016-10-07 18:16 ` Markus Armbruster
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=1475842159-26039-13-git-send-email-armbru@redhat.com \
--to=armbru@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).