From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: mtk.manpages@gmail.com
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: [PATCH] execveat.2: srcfix
Date: Thu, 31 Dec 2020 00:28:08 +0100 [thread overview]
Message-ID: <bdda57ff-acdd-9109-5720-ba0db8138d41@gmail.com> (raw)
In-Reply-To: <CAKgNAkjf8gS5Av2pzYqt_JHjjnCw-FrjqQicjhr20+MzgsK3Xg@mail.gmail.com>
On 12/30/20 11:27 PM, Michael Kerrisk (man-pages) wrote:
> Hi Alex,
>
> On Wed, 30 Dec 2020 at 22:41, Alejandro Colomar <alx.manpages@gmail.com> wrote:
>>
>> Use .nf/.fi in the SYNOPSIS.
>
> I'm not against the patch. But why this particular page?
Hello Michael,
I fixed this while adding the notes about missing headers in that page,
but I felt that it was better as a separate patch.
And the other patch I didn't send it in the last moment as I found a
missing line :p
Would you prefer a global fix about .nf/.fi or just fix as we go?
Cheers,
Alex
>
> Thanks,
>
> Michael
>
>>
>> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
>> ---
>>
>> man2/execveat.2 | 11 ++++++-----
>> 1 file changed, 6 insertions(+), 5 deletions(-)
>>
>> diff --git a/man2/execveat.2 b/man2/execveat.2
>> index 7c31d8f17..c5cd843f9 100644
>> --- a/man2/execveat.2
>> +++ b/man2/execveat.2
>> @@ -27,13 +27,13 @@
>> .SH NAME
>> execveat \- execute program relative to a directory file descriptor
>> .SH SYNOPSIS
>> +.nf
>> .B #include <unistd.h>
>> .PP
>> -.BI "int execveat(int " dirfd ", const char *" pathname ","
>> -.br
>> -.BI " char *const " argv "[], char *const " envp "[],"
>> -.br
>> +.BI "int execveat(int " dirfd ", const char *" pathname ,
>> +.BI " char *const " argv "[], char *const " envp [],
>> .BI " int " flags );
>> +.fi
>> .SH DESCRIPTION
>> .\" commit 51f39a1f0cea1cacf8c787f652f26dfee9611874
>> The
>> @@ -224,7 +224,8 @@ where scripts recursively employ
>> .\" For an example, see Michael Kerrisk's 2015-01-10 reply in this LKML
>> .\" thread (http://thread.gmane.org/gmane.linux.kernel/1836105/focus=20229):
>> .\"
>> -.\" Subject: [PATCHv10 man-pages 5/5] execveat.2: initial man page.\" for execveat(2
>> +.\" Subject: [PATCHv10 man-pages 5/5] execveat.2: initial man page
>> +.\" for execveat(2)
>> .\" Date: Mon, 24 Nov 2014 11:53:59 +0000
>> .SH SEE ALSO
>> .BR execve (2),
>> --
>> 2.29.2
>>
>
>
next prev parent reply other threads:[~2020-12-30 23:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 21:41 [PATCH] execveat.2: srcfix Alejandro Colomar
2020-12-30 22:27 ` Michael Kerrisk (man-pages)
2020-12-30 23:28 ` Alejandro Colomar (man-pages) [this message]
2020-12-31 10:06 ` Michael Kerrisk (man-pages)
2020-12-31 12:28 ` Alejandro Colomar (man-pages)
2020-12-31 15:26 ` Michael Kerrisk (man-pages)
2020-12-31 18:55 ` Alejandro Colomar (man-pages)
2020-12-31 23:29 ` Alejandro Colomar (man-pages)
2021-01-01 11:43 ` Michael Kerrisk (man-pages)
2021-01-01 11:41 ` Michael Kerrisk (man-pages)
2021-01-01 13:49 ` Alejandro Colomar (man-pages)
2021-01-01 22:29 ` Michael Kerrisk (man-pages)
2021-01-02 16:03 ` Alejandro Colomar (man-pages)
2021-01-02 19:59 ` Michael Kerrisk (man-pages)
2021-01-02 21:40 ` Alejandro Colomar (man-pages)
2021-01-03 12:11 ` Michael Kerrisk (man-pages)
2021-01-04 12:59 ` Alejandro Colomar (man-pages)
2021-01-04 13:21 ` Michael Kerrisk (man-pages)
2021-02-02 17:43 ` Alejandro Colomar (man-pages)
2021-02-13 19:15 ` Michael Kerrisk (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=bdda57ff-acdd-9109-5720-ba0db8138d41@gmail.com \
--to=alx.manpages@gmail.com \
--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