From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH RESEND v3 0/2] -blockdev documentation
Date: Fri, 16 Jun 2017 17:54:32 +0200 [thread overview]
Message-ID: <1497628474-13275-1-git-send-email-kwolf@redhat.com> (raw)
This series was posted as part of my -blockdev prototype implementation back in
September 2016 and already received review. When Markus merged his final
implementation of -blockdev, no real documentation was added, so even though my
implementation isn't needed any more, we still need these doc patches.
There is nothing new in here, I'm only reposting the series to notify everyone
that I'm including the patches in my block tree now.
Kevin Wolf (2):
doc: Document generic -blockdev options
doc: Document driver-specific -blockdev options
qemu-options.hx | 221 ++++++++++++++++++++++++++++++++++++++++++++++++--------
1 file changed, 192 insertions(+), 29 deletions(-)
--
1.8.3.1
next reply other threads:[~2017-06-16 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 15:54 Kevin Wolf [this message]
2017-06-16 15:54 ` [Qemu-devel] [PATCH RESEND v3 1/2] doc: Document generic -blockdev options Kevin Wolf
2017-06-16 15:54 ` [Qemu-devel] [PATCH RESEND v3 2/2] doc: Document driver-specific " Kevin Wolf
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=1497628474-13275-1-git-send-email-kwolf@redhat.com \
--to=kwolf@redhat.com \
--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).