qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>, qemu-devel@nongnu.org
Cc: jan.kiszka@siemens.com, thuth@redhat.com, jasowang@redhat.com,
	armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCHv2] slirp: Allow disabling IPv4 or IPv6
Date: Thu, 24 Mar 2016 16:19:53 -0600	[thread overview]
Message-ID: <56F46809.8020106@redhat.com> (raw)
In-Reply-To: <1458857568-24854-1-git-send-email-samuel.thibault@ens-lyon.org>

[-- Attachment #1: Type: text/plain, Size: 2176 bytes --]

On 03/24/2016 04:12 PM, Samuel Thibault wrote:
> Add ipv4 and ipv6 boolean options, so the user can setup IPv4-only and
> IPv6-only network environments.
> 
> Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org>

Please mention in the commit message that you are renaming
recently-added members, and therefore this MUST be done in 2.6 before we
bake in the old naming, as part of your commit...

> 
> ---
> 
> Changes since previous versions:
> 
> - Introduce boolean options ipv4 and ipv6 instead of net=none and
>   ip6-net=none.
> - Rename ipv6 options to ipv6-foo instead of ip6-foo, to make it coherent
>   with the new ipv6 option (itself coherent with the other ipv6 options)

...rather than just a parenthetical note that gets lost during 'git am'.

In fact, I'd probably split it into two patches: one to rename existing
s/ip6-/ipv6-/ members, and the other to add new boolean members.

> +++ b/qapi-schema.json
> @@ -2425,9 +2425,18 @@
>  #
>  # @restrict: #optional isolate the guest from the host
>  #
> +# @ipv4: #optional whether to support IPv4, default is to support both
> +# IPv4 and IPv6 (since 2.6)

The last part is long; maybe:

..., default true for enabled (since 2.6)

> +#
> +# @ipv6: #optional whether to support IPv6, default is to support both
> +# IPv4 and IPv6 (since 2.6)

and again.

> +#
>  # @ip: #optional legacy parameter, use net= instead
>  #
> -# @net: #optional IP address and optional netmask
> +# @net: #optional IP network address that the guest will see, in the
> +# form addr[/netmask] (default is 10.0.2.0/24). The netmask is optional,
> +# and can be either in the form a.b.c.d or as a number of valid top-most
> +# bits.

Many QAPI commands do hanging indents, as in:

# @net: #optional IP network address that the guest will see, in the
#       form addr[/netmask] (default is 10.0.2.0/24). The netmask is
#       optional, and can ...

so that it is easier to spot the next member's documentation.  But I
don't think it is a strict requirement.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

      reply	other threads:[~2016-03-24 22:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24 22:12 [Qemu-devel] [PATCHv2] slirp: Allow disabling IPv4 or IPv6 Samuel Thibault
2016-03-24 22:19 ` Eric Blake [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=56F46809.8020106@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=jasowang@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=thuth@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).