From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man <linux-man@vger.kernel.org>
Subject: Re: [PATCH] execveat.2: srcfix
Date: Mon, 4 Jan 2021 14:21:33 +0100 [thread overview]
Message-ID: <dc1f381b-9f9f-9145-f794-d73eab90f601@gmail.com> (raw)
In-Reply-To: <a2fc82ef-1c08-b7bb-bbcc-f95e44472b79@gmail.com>
Hi Alex,
On 1/4/21 1:59 PM, Alejandro Colomar (man-pages) wrote:
> Hi Michael,
>
> On 1/3/21 1:11 PM, Michael Kerrisk (man-pages) wrote:
>> Hi Alex,
>>
>> On 1/2/21 10:40 PM, Alejandro Colomar (man-pages) wrote:
[...]
>>> circleq.3, list.3, slist.3, tailq.3, stailq.3: group?
>>
>> I've taken a shot at that. You may have improvements to
>> suggest, or even reorderings to suggest (as patches).
>
> I'd group _FIRST, _LAST, _NEXT, _PREV; or at least _FIRST with _LAST.
> And I don't know which ordering to use within that group.
> Any ideas? FLNP? FNPL? FPNL? FL NP? NP FL?
> To be consistent with the ordering you used for _INSERT_,
> we could use 'NP FL',
> and put those 2 groups after the 2 _INSERT_ groups.
I'll go with whatever you think is best. Maybe FLPN?
>
>>> exec.3: consistency with commas; execvpe can be joined
>> Done; done
>
> wsfix: g/char */s//char */
Fixed.
[...]
>>> xdr.3: wsfix: g/) (/s//)(/
>>> (See if there are any other pages with this
>>> that I may haven't seen.)
>>
>> Done.
>>
>> Plus: error.3, ftw.3, glob.3, pthread_create.3, rpc.3
>
> A few more:
> signal.3 (NOTES)
For better or worse, I think the author there was using extravagant
white space to make the signature easier to read. I'll leave as is.
> malloc_hook.3 (EXAMPLES)
Fixed.
[...]
>>> isw*.3: Rewrite into one page similar to isalpha.3?
>>> Does it really need so many pages?
>>
>> There sure is a lot of repetition across those pages...
>
> I'll add it to my TODO list.
I took another look at those pages, and decided they are not as
repetitious as they first appear. I'm not sure there's anything
actuilly yo do there.
[...]
Thanks,
Michael
--
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:[~2021-01-04 13:22 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)
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) [this message]
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=dc1f381b-9f9f-9145-f794-d73eab90f601@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.