From: Stefan Hajnoczi <stefanha@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH] docs: add qemu-block-drivers(7) man page
Date: Tue, 27 Jun 2017 11:56:54 +0100 [thread overview]
Message-ID: <20170627105654.GA5364@stefanha-x1.localdomain> (raw)
In-Reply-To: <f274e0eb-ec19-346d-2c64-07ee6b30ca69@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
On Mon, Jun 26, 2017 at 04:40:58PM -0400, John Snow wrote:
>
>
> On 06/22/2017 08:17 AM, Stefan Hajnoczi wrote:
> > Block driver documentation is available in qemu-doc.html. It would be
> > convenient to have documentation for formats, protocols, and filter
> > drivers in a man page.
> >
> > Extract the relevant part of qemu-doc.html into a new file called
> > docs/qemu-block-drivers.texi. This file can also be built as a
> > stand-alone document (man, html, etc).
> >
> > Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
>
> Thanks, this is really useful information to have. Looks good to me, but
> Paolo's changes prevent it from applying now.
>
> So, as of last week:
>
> Reviewed-by: John Snow <jsnow@redhat.com>
Thanks for the reminder. Will rebase and resend.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2017-06-27 10:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 12:17 [Qemu-devel] [PATCH] docs: add qemu-block-drivers(7) man page Stefan Hajnoczi
2017-06-26 20:40 ` [Qemu-devel] [Qemu-block] " John Snow
2017-06-27 10:56 ` Stefan Hajnoczi [this message]
2017-06-27 15:20 ` [Qemu-devel] " Eric Blake
2017-07-05 13:05 ` Stefan Hajnoczi
2017-07-05 16:08 ` Paolo Bonzini
2017-07-10 9:52 ` Stefan Hajnoczi
2017-07-10 10:00 ` Paolo Bonzini
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=20170627105654.GA5364@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=jsnow@redhat.com \
--cc=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).