From: Stephen Kitt <steve@sk2.org>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org,
Michael Kerrisk <mtk.manpages@gmail.com>,
Christian Brauner <christian.brauner@ubuntu.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] close_range.2: new page documenting close_range(2)
Date: Thu, 10 Dec 2020 09:21:33 +0100 [thread overview]
Message-ID: <20201210092047.4853db82@heffalump.sk2.org> (raw)
In-Reply-To: <e50183ce-3ccb-c41c-9d30-bfb622b3b1f5@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2221 bytes --]
Hi Alejandro,
On Thu, 10 Dec 2020 01:24:28 +0100, "Alejandro Colomar (man-pages)"
<alx.manpages@gmail.com> wrote:
> A few more comments below.
Thanks for all the detailed reviews! (Same goes to everyone reviewing this
yesterday, thanks for helping turn my not-so-great attempt into something
really useful.)
> Michael, please have a look at them too.
>
> Christian, do you have any program that you used to test the syscall
> that could be added as an example program to the page?
I have some example code that I could turn into an example program, but I
imagine Christian has better code than me ;-).
> > +.BI "int close_range(unsigned int " first ", unsigned int " last ",
> > unsigned int " flags );
>
> This line overflows an 80-col terminal. Fix:
>
> .BI "int close_range(unsigned int " first ", unsigned int " last ,
> .BI " unsigned int " flags );
Noted, thanks.
> > +.fi
>
> Please, add a note here that there is no wrapper for this syscall,
> as in other syscalls without wrapper (see membarrier(2) as an example).
> That way it's easier to grep, if all pages have the same notice.
Ah, right, I used pidfd_open(2) as an example, where it's mentioned later.
> Please use semantic newlines.
> See man-pages(7)::STYLE GUIDE::Use semantic newlines
Noted, thanks.
> > +.SH NOTES
> > +Currently, there is no glibc wrapper for this system call; call it using
> > +.BR syscall (2).
>
> I can see that this notice is also present on a few pages,
> but the one in membarrier(2) is more extended.
>
> Please, copy the notices from membarrier(2).
> There's one in SYNOPSIS, and one in NOTES.
Will do!
> > +.SH USE CASES
>
> This section is unconventional. Please move that text to one of the
> traditional sections. I think DESCRIPTION would be the best place for this.
>
> For a list of the traditional sections,
> see man-pages(7)::DESCRIPTION::Sections within a manual page
Indeed; it grew out of pidfd_open's "Use cases" section but making all this
part of the description would be much better.
I'll wait and see if there are other comments, and send a v3 addressing all
the above.
Regards,
Stephen
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-12-10 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 22:00 [PATCH v2] close_range.2: new page documenting close_range(2) Stephen Kitt
2020-12-10 0:24 ` Alejandro Colomar (man-pages)
2020-12-10 8:21 ` Stephen Kitt [this message]
2020-12-10 23:02 ` Michael Kerrisk (man-pages)
2020-12-12 12:16 ` Christian Brauner
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=20201210092047.4853db82@heffalump.sk2.org \
--to=steve@sk2.org \
--cc=alx.manpages@gmail.com \
--cc=christian.brauner@ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.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