linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Sat, 2 Jan 2021 22:40:25 +0100	[thread overview]
Message-ID: <31e06e88-808c-2212-9853-f8e7bd9262a8@gmail.com> (raw)
In-Reply-To: <CAKgNAkiUZoV1aE10=6ehkqCKwpzrmbYt_fTjGGBEGi9=HZh7Gg@mail.gmail.com>

Hi Michael,

I read everything this time ;)

On 1/2/21 8:59 PM, Michael Kerrisk (man-pages) wrote:
> HI Alex,
> 
> On Sat, 2 Jan 2021 at 17:04, Alejandro Colomar (man-pages)
> <alx.manpages@gmail.com> wrote:
>>
>> Hi Michael,
>>
>> On 1/1/21 11:29 PM, Michael Kerrisk (man-pages) wrote:
>>> Hi Alex,
>> [...]>>>> login.3: group
>>>>
>>>> ffix!!
>>>
>>> Done.
>>>
>>>> The following may help:
>>>>
>>>> $ for p in $(git grep -l '.SH SYN' man?); do \
>>>>      echo "===================== $p"; \
>>>>      man -l $p  2> /dev/null \
>>>>      |sed -n '/^SYNOP/,/DESCR/p' \
>>>>      |sed '/Feat/,$d'; \
>>>>   done \
>>>>   |grep '); *[a-zA-Z_]' \
>>>>   |grep -v -e 'Note:' -e NOTES;
>>>>        int brk(void *addr); void *sbrk(intptr_t increment);
>>>>        set);  ssize_t  pwrite(int  fd,  const  void *buf, size_t
>>>>        long a64l(const char *str64); char *l64a(long value);
>>>>        double fmax(double x, double  y);  float  fmaxf(float  x,
>>>>        float  y);  long  double fmaxl(long double x, long double
>>>>        void  login(const struct utmp *ut); int logout(const char
>>>>               place the result(s); inproc is used to encode  the
>>>>               dress  of  where to place the result(s); inproc is
>>>>               ter(s); procname should return a  pointer  to  its
>>>>               static result(s); inproc is used to decode the pa‐
>>>>               RPC socket(s); rdfds is the  resultant  read  file
>>>>        int wordexp(const char *s, wordexp_t *p, int flags); void
>>>>               sp,MAXUN.UNSIGNED ); where MAXUN.UNSIGNED  is  the
>>>>                                     (SIGEV_THREAD_ID); Linux-specific */
>>>
>>> Thanks. I fixed a few things.
>>>
>>
>> wordexp.3 is still broken.
> 
> Thanks. Fixed now.
> 
>>>>>> I didn't read past that.
>>>>
>>>> Still I didn't read past that :)
>>
>> Later I'll have a look past there :)
> 
> That would be great!

adjtimex.2: compact
getpeername.2: 78-col
kexec_load.2: compact?
msgop.2: compact
rt_sigqueueinfo.2: Join + compact
sgetmask.2: compact
subpage_prot.2: Join
vm86.2: compact

circleq.3, list.3, slist.3, tailq.3, stailq.3: group?
des_crypt.3: group
drand48_r.3: Join
error.3: group
ether_aton.3: group
exec.3: consistency with commas; execvpe can be joined
fseeko.3: compact

resolver.3: group?
rewinddir.3: compact headers
rpc: 78-col
	CLGET_SERVER_ADDR  struct sockaddr_in  // get server's addre
	ss
rtnetlink.3: group or compact; 78-col
scandir.3:
	scandir(): move 'filter' and 'compar' 1 char to the right
	  so that parentheses are not aligned and confuse.
	  It still fits 1 char to the right but not to for a 78-col.
	group?
	scandirat(): ffix!!: namelist can be joined
setaliasent.3: move more to the right
shm_open.3: compact
sigpause.3: compact
sigset.3: group
strstr.3: compact #define & #include
termios.3: group even more?
timegm.3: compact
unlocked_stdio.3: Join fread_unlocked(3)? Or not?
xdr.3: wsfix: g/) (/s//)(/
	(See if there are any other pages with this
	 that I may haven't seen.)

man.7: group or compact
rtnetlink.7: 78-col
sigevent.7: s/) (/)(/
	If you move the comments a few chars to the right (3<=x<=6),
	  you will compact one line

Also, curiously execveat(2), which is the one that started all this,
didn't look bad :p
So we'll have to grep for .nf/.fi too after this.



Things to note for other patches:

isw*.3: Rewrite into one page similar to isalpha.3?
	Does it really need so many pages?
recno.3: Review: no APIs
string.3: What is the criterion for functions to be there?
	Also, there are functions which are already documented
	  in their own pages (see strcpy(3))
	Some others don't appear there (see memcpy(3)
	  eventhough they are in string.h.



Cheers,

Alex


> 
> Cheers,
> 
> Michael
> 

-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

  reply	other threads:[~2021-01-02 21:41 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) [this message]
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=31e06e88-808c-2212-9853-f8e7bd9262a8@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;
as well as URLs for NNTP newsgroup(s).