From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Stephen Kitt <steve@sk2.org>
Cc: linux-man@vger.kernel.org,
Michael Kerrisk <mtk.manpages@gmail.com>,
Christian Brauner <christian.brauner@ubuntu.com>,
Giuseppe Scrivano <gscrivan@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] close_range.2: new page documenting close_range(2)
Date: Mon, 21 Dec 2020 20:33:06 +0100 [thread overview]
Message-ID: <cd13ed9f-4156-d76d-c485-9d67ea610ce2@gmail.com> (raw)
In-Reply-To: <20201221202425.168fdaaf@heffalump.sk2.org>
Hi Stephen,
On 12/21/20 8:24 PM, Stephen Kitt wrote:
> Hi Alex,
>
> On Sat, 19 Dec 2020 15:00:00 +0100, "Alejandro Colomar (man-pages)"
> <alx.manpages@gmail.com> wrote:
>> On 12/18/20 5:58 PM, Stephen Kitt wrote:
> [...]
>>> +This program executes the command given on its command-line after
>>> +opening the files listed after the command,
>>> +and then using
>>
>> s/using/uses/
>
> It’s the same form as “opening”: “after opening ... and then using”. The
> overall sequence is “open”, “close_range”, “execve”.
>
> Regards,
>
> Stephen
>
Ahhh. Then I think the comma is misleading.
What about the following?:
On 12/18/20 5:58 PM, Stephen Kitt wrote:
> +.PP
> +This program executes the command given on its command-line after
> +opening the files listed after the command,
> +and then using
> +.B close_range
> +to close them:
This program executes the command given on its command line,
after opening the files listed after the command
and then using *close_range()* to close them:
Thanks,
Alex
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2020-12-21 19:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 16:58 [PATCH v3] close_range.2: new page documenting close_range(2) Stephen Kitt
2020-12-19 14:00 ` Alejandro Colomar (man-pages)
2020-12-20 22:00 ` Stephen Kitt
2020-12-21 8:32 ` Alejandro Colomar (man-pages)
2020-12-21 19:24 ` Stephen Kitt
2020-12-21 19:33 ` Alejandro Colomar (man-pages) [this message]
2020-12-21 19:45 ` 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=cd13ed9f-4156-d76d-c485-9d67ea610ce2@gmail.com \
--to=alx.manpages@gmail.com \
--cc=christian.brauner@ubuntu.com \
--cc=gscrivan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).