All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] unix.7: add example
Date: Wed, 6 Jan 2016 22:06:21 +0100	[thread overview]
Message-ID: <568D81CD.5010508@gmx.de> (raw)
In-Reply-To: <568D277D.5000205-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On 01/06/2016 03:41 PM, Michael Kerrisk (man-pages) wrote:
> Hello Heinrich,
>
> On 01/05/2016 04:17 PM, Heinrich Schuchardt wrote:
>> A complete example demonstrating the usage of sockets for local
interprocess
>> communication is added.
>
> Thanks for doing this. I'm happy to take such a piece for the page, but
> I think things could be improved a little.
>

Hello Michael,

thank you for reviewing. I will update the patch.

http://pubs.opengroup.org/onlinepubs/009695399/functions/recv.html
has the following sentence:

The recv() function is equivalent to recvfrom() with a zero address_len
argument, and to read() if no flags are used.

Shouldn't we add this information to recv.2?

Send.2 documents the equivalences.

Best regards

Heinrich


--
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:[~2016-01-06 21:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-05 15:17 [PATCH] unix.7: add example Heinrich Schuchardt
     [not found] ` <1452007033-26166-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
2016-01-06 14:41   ` Michael Kerrisk (man-pages)
     [not found]     ` <568D277D.5000205-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-01-06 21:06       ` Heinrich Schuchardt [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=568D81CD.5010508@gmx.de \
    --to=xypron.glpk-mmb7mzphnfy@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-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.