public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] epoll_ctl.2: replace input flag footnotes with a list section
Date: Thu, 13 Jan 2022 14:08:28 +0100	[thread overview]
Message-ID: <dcfa6694-fa4e-11c9-b146-e9d2e4b5cd3f@gmail.com> (raw)
In-Reply-To: <20220113022755.qs32mcusuuca6dv3@tarta.nabijaczleweli.xyz>

Hi, наб!

On 1/13/22 03:27, наб wrote:
> This is shorter, clearly separates the events from the flags,
> and more consistent (cf. EPOLLEXCLUSIVE which has a different message
> than the rest)
> 
> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
> ---
>   man2/epoll_ctl.2 | 33 +++------------------------------
>   1 file changed, 3 insertions(+), 30 deletions(-)
> 
> diff --git a/man2/epoll_ctl.2 b/man2/epoll_ctl.2
> index ec31cac72..c9f9649a5 100644
> --- a/man2/epoll_ctl.2
> +++ b/man2/epoll_ctl.2
> @@ -156,6 +156,9 @@ Note that when reading from a channel such as a pipe or a stream socket,
>   this event merely indicates that the peer closed its end of the channel.
>   Subsequent reads from the channel will return 0 (end of file)
>   only after all outstanding data in the channel has been consumed.
> +.PP
> +And one of the following input flags, which are never returned by

This sentence (as I understand it) is a continuation of _"The  events 
member of the epoll_event structure is a bit mask composed by ORing 
together zero or more of the following available event types:"_, right?

So, the bitmask is composed by _zero or more_ event types, and _exactly 
one_ input flags?  Just asking, I don't know the syscall.  I think we 
should mix both sentences into a single one where it is very clear what 
the bitmask is composed of.  And then a simple introduction sentence 
like: "The available event types are:"  and then below the event types 
another similar one for introducing the input flags.

Your thoughts?

Thanks,

Alex


-- 
Alejandro Colomar
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

  reply	other threads:[~2022-01-13 13:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13  2:27 [PATCH] epoll_ctl.2: replace input flag footnotes with a list section наб
2022-01-13 13:08 ` Alejandro Colomar (man-pages) [this message]
2022-01-13 15:14   ` [PATCH v2] " наб
2022-01-13 20:37     ` Alejandro Colomar (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=dcfa6694-fa4e-11c9-b146-e9d2e4b5cd3f@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=nabijaczleweli@nabijaczleweli.xyz \
    /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