Re: [PATCH v3] close_range.2: new page documenting close_range(2)

[Stephen Kitt <steve@sk2.org>]

[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]

Hi Alex,

On Mon, 21 Dec 2020 20:33:06 +0100, "Alejandro Colomar (man-pages)"
<alx.manpages@gmail.com> wrote:
> On 12/21/20 8:24 PM, Stephen Kitt wrote:
> > 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”.
> 
> 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:

Yes, that works better.

I’ll follow up with a v5 with just that change.

Regards,

Stephen

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]