From: Markus Armbruster <armbru@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, marcandre.lureau@redhat.com,
thuth@redhat.com, peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PATCH] docs: create interop/ subdirectory
Date: Tue, 06 Jun 2017 18:28:03 +0200 [thread overview]
Message-ID: <871sqxjd2k.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20170606151757.32473-1-pbonzini@redhat.com> (Paolo Bonzini's message of "Tue, 6 Jun 2017 17:17:57 +0200")
Paolo Bonzini <pbonzini@redhat.com> writes:
> This is for the future interoperability & management guide. It includes
> the QAPI docs, including the automatically generated ones, other socket
> protocols (vhost-user, VNC), and the qcow2 file format.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
No objections to adding a bit more structure to docs/ this way. Can't
say I like the name interop/, though. Oh well, it's not my bikeshed to
paint :)
next prev parent reply other threads:[~2017-06-06 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 15:17 [Qemu-devel] [PATCH] docs: create interop/ subdirectory Paolo Bonzini
2017-06-06 15:24 ` no-reply
2017-06-06 16:28 ` Markus Armbruster [this message]
2017-06-06 16:29 ` Peter Maydell
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=871sqxjd2k.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.