linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: [PATCH] execveat.2: srcfix
Date: Sat, 2 Jan 2021 17:03:58 +0100	[thread overview]
Message-ID: <40f1140a-496b-5b2b-c1de-4522b1ea5043@gmail.com> (raw)
In-Reply-To: <8c66c28d-2ff1-b629-33f9-df057998f80e@gmail.com>

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.

>>>
>>>> I didn't read past that.
>>
>> Still I didn't read past that :)

Later I'll have a look past there :)
Cheers,

Alex

> 
> ;-)
> 
>>> Well thanks! What you did read was helpful!
>>
>> Thanks!
>>
>> I removed from the reply those already fixed,
>> so what you see in this email is still pending
>> (minus a few that I may have forgotten to remove).
> 
> Thanks again, Alex. I've pushed the fixed I made.
> 
> 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 16:04 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) [this message]
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=40f1140a-496b-5b2b-c1de-4522b1ea5043@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).