qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Wouter Verhelst <w@uter.be>
To: Alex Bligh <alex@alex.org.uk>
Cc: "nbd-general@lists.sourceforge.net"
	<nbd-general@lists.sourceforge.net>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Nbd] [PATCHv2] Amend NBD_OPT_SELECT (now NBD_OPT_INFO) and NBD_OPT_GO documentation
Date: Tue, 5 Apr 2016 23:03:17 +0200	[thread overview]
Message-ID: <20160405210317.GE13913@grep.be> (raw)
In-Reply-To: <1459888946-27233-1-git-send-email-alex@alex.org.uk>

On Tue, Apr 05, 2016 at 09:42:26PM +0100, Alex Bligh wrote:
> Amend the NBD_OPT_SELECT and NBD_OPT_GO documentation as
> follows:
> 
> * Change NBD_OPT_SELECT to be called NBD_OPT_INFO
> 
> * Remove the 'selection' aspect of that command, so that
>   it now merely returns information. This is to avoid
>   the server storing state.
> 
> * Allow a name to be specified on NBD_OPT_GO
> 
> * Make clear the rules for default device selection
> 
> * Remove the provision concerning TLS resetting device selection
> 
> * Remove NBD_REP_ERR_INVALID as a reply to NBD_OPT_GO as there
>   is now no necessity for a prior NBD_OPT_INFO
> 
> * Make it clear NBD_OPT_GO is in effect a better alternative
>   for NBD_OPT_EXPORT_NAME
> 
> * Make it clear the NBD_OPT_INFO and NBD_OPT_GO are in
>   essence the same command, save that NBD_OPT_GO puts you
>   into transmission mode if successful.
> 
> * Clarify permitted option returns outside TLS to prevent
>   export enumeration.
> 
> * Remove 'length' 32 bit quantity from
>   NBD_OPT_SELECT (and don't copy it into NBD_OPT_GO) so it
>   looks exactly like NBD_OPT_EXPORT_NAME bar the reply.
>   This length is unnecessary as it's in the option header
>   anyway.
> 
> * Reorder the fields of an NBD_OPT_INFO / NBD_OPT_GO reply
>   so the variable length elements are at the end.
> 
> * Make the documentation much more concise.
> 
> Signed-off-by: Alex Bligh <alex@alex.org.uk>
[...]

applied, thanks.

-- 
< ron> I mean, the main *practical* problem with C++, is there's like a dozen
       people in the world who think they really understand all of its rules,
       and pretty much all of them are just lying to themselves too.
 -- #debian-devel, OFTC, 2016-02-12

  reply	other threads:[~2016-04-05 21:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05 20:42 [Qemu-devel] [PATCHv2] Amend NBD_OPT_SELECT (now NBD_OPT_INFO) and NBD_OPT_GO documentation Alex Bligh
2016-04-05 21:03 ` Wouter Verhelst [this message]
2016-04-05 21:26   ` [Qemu-devel] [Nbd] " Eric Blake
2016-04-05 23:30     ` Alex Bligh
2016-04-06  9:26     ` Alex Bligh
2016-04-05 21:25 ` [Qemu-devel] " Eric Blake

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=20160405210317.GE13913@grep.be \
    --to=w@uter.be \
    --cc=alex@alex.org.uk \
    --cc=nbd-general@lists.sourceforge.net \
    --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).