From: "Daniel P. Berrange" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, el13635@mail.ntua.gr
Subject: Re: [Qemu-devel] [PATCH v3] docs: add qemu-block-drivers(7) man page
Date: Wed, 26 Jul 2017 14:09:13 +0100 [thread overview]
Message-ID: <20170726130913.GM7620@redhat.com> (raw)
In-Reply-To: <20170726130337.24102-1-stefanha@redhat.com>
On Wed, Jul 26, 2017 at 02:03:37PM +0100, 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).
Is there perhaps benefit it taking it further and creating one
man page per block driver. Many of the block drivers are optional
and can be turned off, so this would let us leave out the docs
for disabled block drivers too.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-07-26 13:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 13:03 [Qemu-devel] [PATCH v3] docs: add qemu-block-drivers(7) man page Stefan Hajnoczi
2017-07-26 13:09 ` Daniel P. Berrange [this message]
2017-07-27 10:12 ` Stefan Hajnoczi
2017-07-27 10:13 ` Daniel P. Berrange
2017-07-27 11:37 ` Kevin Wolf
2017-07-31 15:56 ` Eric Blake
2017-07-31 15:59 ` Kevin Wolf
2017-09-04 16:34 ` 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=20170726130913.GM7620@redhat.com \
--to=berrange@redhat.com \
--cc=el13635@mail.ntua.gr \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 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).