From: Kevin Wolf <kwolf@redhat.com>
To: ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: qemu-devel@nongnu.org, Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] Documentation: Add syntax for using sheepdog devices
Date: Mon, 31 Oct 2011 09:04:56 +0100 [thread overview]
Message-ID: <4EAE56A8.8030306@redhat.com> (raw)
In-Reply-To: <CAN05THT-0SmUZqzqpZoN+gjw99xwv4TycdasGgKvknqfdv96uA@mail.gmail.com>
Am 29.10.2011 05:40, schrieb ronnie sahlberg:
> Hi Kevin,
>
> I agree that maybe we should have a link from the TOC down to the
> "Device URL Syntax".
> I can create a patch to do so.
>
> For moving the existing "Device URL Syntax" information into "3.6 Disk
> Images", I am not sure.
> I think both have their place and they serve different purposes even
> if there is some overlap.
>
> Device URL Syntax:
> This contains a terse description of the syntax on how to specify
> these devices on the command line.
> This is really needed in the manpage.
> Very basic syntax description and an example command line or two.
>
> Qemu-doc:
> I see as much more detailed documentation than a simple manpage. It
> also includes "howto" type descriptions that show how to set it up
> end-to-end from creating a device image, how to configure a basic NDB
> server, and then how to make it available to QEMU.
> This I think is more a full end-to-end description with howto examples.
>
> I think it would make sense to have both.
>
> What do you think?
> If you agree this makes sense I will continue adding terse sections to
> "Device URL Syntax" but also start going through section "3.6" and
> make sure we also have "howto-like" examples on how to set it up on
> the server side as well.
> A section in 3.6 for iscsi could for example show how to create an
> image and export via STGT so that QEMU can access it as an iscsi lun.
Sure, that sounds good. I just had the impression that currently the
"terse" URL syntax description is in fact more extensive than section
3.6 which should be the full documentation.
Kevin
prev parent reply other threads:[~2011-10-31 8:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 9:13 [Qemu-devel] [PATCH 0/0] Manpage. Fix typo and add Sheepdog description Ronnie Sahlberg
2011-10-28 9:13 ` [Qemu-devel] [PATCH 1/2] Documentation: Fix typo in manpage. NDB -> NBD Ronnie Sahlberg
2011-10-28 9:24 ` Kevin Wolf
2011-10-28 9:13 ` [Qemu-devel] [PATCH 2/2] Documentation: Add syntax for using sheepdog devices Ronnie Sahlberg
2011-10-28 9:13 ` Eric Sunshine
2011-10-28 9:32 ` Kevin Wolf
2011-10-29 3:40 ` ronnie sahlberg
2011-10-31 8:04 ` Kevin Wolf [this message]
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=4EAE56A8.8030306@redhat.com \
--to=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.com \
--cc=sunshine@sunshineco.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).