From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Stefan Puiu <stefan.puiu-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
lnx-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH] inet_pton.3: Mention byte order
Date: Wed, 18 May 2016 22:36:20 +0200 [thread overview]
Message-ID: <c7e11344-b0ab-3ec0-49e4-0e66bc3f9530@gmail.com> (raw)
In-Reply-To: <CACKs7VAgKPUOp7+_0NzWujruw0fsMF0L+UnsNqV=zsfmF+tqrw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hello Stefan,
On 05/12/2016 09:16 AM, Stefan Puiu wrote:
> Hi,
>
> I was a bit stumped recently to realize that both inet_ntop() and
> inet_pton() work with addresses in network byte order.
Yes, that's correct.
> inet_ntop.3
> mentions that, and the example from inet_pton(), as far as I can tell,
> implies that you can call inet_ntop() on the result of inet_pton(), so
> the byte order needs to match, but I think it's better to mention this
> explicitly in the man page text.
Yes, it should be mentioned.
> How about this (patch against git)?
Following up in next mail...
Cheers,
Michael
> diff --git a/man3/inet_pton.3 b/man3/inet_pton.3
> index 4ff16b9..8b1017e 100644
> --- a/man3/inet_pton.3
> +++ b/man3/inet_pton.3
> @@ -64,6 +64,8 @@ and copied to
> which must be
> .I sizeof(struct in_addr)
> (4) bytes (32 bits) long.
> +.IR dst
> +is written in network byte order.
> .TP
> .B AF_INET6
> .I src
>
> Thanks,
> Stefan.
> --
> 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
> .
>
--
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
prev parent reply other threads:[~2016-05-18 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 7:16 [PATCH] inet_pton.3: Mention byte order Stefan Puiu
[not found] ` <CACKs7VAgKPUOp7+_0NzWujruw0fsMF0L+UnsNqV=zsfmF+tqrw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-05-12 7:23 ` Stefan Puiu
[not found] ` <CACKs7VAa+v_0q1JOWOka=g0UiTzyMv-hSKYZZKebm04U5Z1_Jw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-05-18 20:36 ` Michael Kerrisk (man-pages)
2016-05-18 20:36 ` Michael Kerrisk (man-pages) [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=c7e11344-b0ab-3ec0-49e4-0e66bc3f9530@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=stefan.puiu-Re5JQEeQqe8AvxtiuMwx3w@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.