From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>,
Stephen Kitt <steve@sk2.org>
Cc: mtk.manpages@gmail.com, linux-man <linux-man@vger.kernel.org>,
Christian Brauner <christian.brauner@ubuntu.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch] close_range.2: new page documenting close_range(2)
Date: Thu, 10 Dec 2020 23:40:37 +0100 [thread overview]
Message-ID: <4542e216-3648-8dc4-0753-5d7379ee599b@gmail.com> (raw)
In-Reply-To: <9cd2dd3a-c87e-e019-00ad-72ace5469338@gmail.com>
On 12/9/20 10:47 AM, Alejandro Colomar (man-pages) wrote:
>>> +descriptors in
>>> +.B /proc/self/fd/
>
> By reading proc.5, I think this should s/.B/.I/, right mtk?
>
>>> +and calling
>>> +.BR close (2)
>>> +on each one.
>>> +.BR close_range ()
>>> +can take care of this without requiring
>>> +.B /proc
>
> By reading proc.5, I think this should s/.B/.I/, right mtk?
Yes to both. Pathnames are formatted with .I.
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2020-12-10 22:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 21:51 [patch] close_range.2: new page documenting close_range(2) Stephen Kitt
2020-12-09 8:50 ` Michael Kerrisk (man-pages)
2020-12-09 9:40 ` Christian Brauner
2020-12-09 9:43 ` Stephen Kitt
2020-12-09 9:47 ` Alejandro Colomar (man-pages)
2020-12-10 22:40 ` Michael Kerrisk (man-pages) [this message]
2020-12-09 9:58 ` Christian Brauner
2020-12-09 10:44 ` Alejandro Colomar (man-pages)
2020-12-09 10:56 ` Christian Brauner
2020-12-10 14:36 ` Alejandro Colomar (man-pages)
2020-12-12 12:14 ` Christian Brauner
2020-12-12 17:58 ` Alejandro Colomar (man-pages)
2020-12-18 10:12 ` Ping: " Alejandro Colomar (man-pages)
2020-12-18 10:14 ` Stephen Kitt
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=4542e216-3648-8dc4-0753-5d7379ee599b@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=christian.brauner@ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=steve@sk2.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox