All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: saulery-GANU6spQydw@public.gmane.org
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	472447-forwarded-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org
Subject: Re: [patch] ipv6.7: documents SOL_IPV6 as an alternative to IPPROTO_IPV6 for socket level.
Date: Wed, 04 Mar 2015 07:24:53 +0100	[thread overview]
Message-ID: <54F6A535.3030103@gmail.com> (raw)
In-Reply-To: <1425424838-17615-1-git-send-email-saulery-GANU6spQydw@public.gmane.org>

Hi Stéphane,

On 03/04/2015 12:20 AM, saulery-GANU6spQydw@public.gmane.org wrote:
> From: Stéphane Aulery <saulery-GANU6spQydw@public.gmane.org>
> 
> Fix for Debian bug #472447 reported by David Madore <david.madore@ens.fr>

I know it's tiresome, but it's nice to have a URL for easy clicking:

https://bugs.debian.org/472447

But, I am skeptical about the bug report. The reporter says that the
page "[does not] mention SOL_IPV6 as an alternative to IPPROTO_IPV6
for socket level.  It would be nice if it could."

This is not a very useful report. *Why* would it be nice? SOL_IPV6 is
not in any standard as far as I can see, nor on any other implementation.
Furthermore, ip(7) says of the analogous "SOL_IP" constant:

       Using  SOL_IP  socket  options  level  isn't  portable, BSD-based
       stacks use IPPROTO_IP level.

So, it appears to me that mentioning SOL_IPV6 is just leading people 
into a portability trap.

In general: one must question bug reports. The reporter may suggest 
that something is true or desirable, but that needs explanation or
justification.

Summary: I won't apply this. (I would entertain a patch that mention 
SOL_IPV6 in NOTES, with a careful note that it is nonportable.)

Cheers,

Michael

> 
> Signed-off-by: Stéphane Aulery <saulery-GANU6spQydw@public.gmane.org>
> ---
>  man7/ipv6.7 | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/man7/ipv6.7 b/man7/ipv6.7
> index c4e6cac..cd1af35 100644
> --- a/man7/ipv6.7
> +++ b/man7/ipv6.7
> @@ -195,7 +195,9 @@ IPv6 supports some protocol-specific socket options that can be set with
>  and read with
>  .BR getsockopt (2).
>  The socket option level for IPv6 is
> -.BR IPPROTO_IPV6 .
> +.BR IPPROTO_IPV6 
> +(or its alternative
> +.BR SOL_IPV6 ).
>  A boolean integer flag is zero when it is false, otherwise true.
>  .TP
>  .B IPV6_ADDRFORM
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2015-03-04  6:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 23:20 [patch] ipv6.7: documents SOL_IPV6 as an alternative to IPPROTO_IPV6 for socket level saulery-GANU6spQydw
     [not found] ` <1425424838-17615-1-git-send-email-saulery-GANU6spQydw@public.gmane.org>
2015-03-04  6:24   ` Michael Kerrisk (man-pages) [this message]
     [not found]     ` <54F6A535.3030103-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-03-04  6:48       ` Stéphane Aulery
2015-03-09 13:04       ` [PATCH] ipv6.7: SOL_IPV6 and other SOL_* options socket are not portable Stéphane Aulery
     [not found]         ` <1425906293-12161-1-git-send-email-saulery-GANU6spQydw@public.gmane.org>
2015-03-22 20:07           ` Stéphane Aulery
2015-03-23  6:17           ` Michael Kerrisk (man-pages)
     [not found]             ` <550FB015.3050504-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-03-23  7:58               ` Stéphane Aulery
     [not found]                 ` <20150323075800.GA1734-GANU6spQydw@public.gmane.org>
2015-03-23  8:16                   ` Michael Kerrisk (man-pages)

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=54F6A535.3030103@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=472447-forwarded-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=saulery-GANU6spQydw@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.