From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, libc-alpha@sourceware.org,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: Re: [PATCH 00/24] man3: SYNOPSIS: Use 'restrict' in prototypes (batch 5)
Date: Fri, 19 Mar 2021 22:08:32 +0100 [thread overview]
Message-ID: <c5b11775-bc89-7e89-33f9-1d56dc8fb92a@gmail.com> (raw)
In-Reply-To: <8d280f7b-034a-3b91-5f50-60bf2cbbcaf3@gmail.com>
Hi Michael,
On 3/14/21 9:53 PM, Michael Kerrisk (man-pages) wrote:
> On 3/14/21 9:51 PM, Michael Kerrisk (man-pages) wrote:
>> Hello Alex,
>>
>> On 3/10/21 7:31 PM, Alejandro Colomar wrote:
>>> This fixes up til trunc.3
>>
>> trunc.3? I'm a little confused, since the last patch is for swab.3.
>>
>>> (I didn't send you scanf.3
>>> in this patch set because I did in my mom's computer and forgot to push).
>>
>> :-).
>>
>>> When you come back and merge all of the pending patches, I'll send/resend
>>> anything that's not in sync anyway.
>>> So don't worry about missing some of them.
>>
>> I've applied all of the below patches.
>>
>> Thanks once again for all of this work!
>
> I forgot to mention that you seem to have made a local fix for a small
> white-space bug in sigwait.3, but didn't send me that patch. Consequently,
> the sigwait.3 patchy didn't apply until I made the same fix.
Yes, when I noticed you weren't able to review all of the emails, I
started buffering most of them, so I only sent you the big "trivial"
patch sets about restrict, and a few other important patches, to avoid
overloading you. While rebasing to reorder them, I lost track of what I
had sent you and what not. We'll sync again soon!
Cheers!
Alex
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2021-03-19 21:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 18:31 Alejandro Colomar
2021-03-10 18:31 ` [PATCH 01/24] sem_getvalue.3: SYNOPSIS: Use 'restrict' in prototypes Alejandro Colomar
2021-03-10 18:31 ` [PATCH 02/24] sem_wait.3: " Alejandro Colomar
2021-03-10 18:31 ` [PATCH 03/24] setaliasent.3: " Alejandro Colomar
2021-03-10 18:31 ` [PATCH 04/24] setbuf.3: " Alejandro Colomar
2021-03-10 18:31 ` [PATCH 05/24] " Alejandro Colomar
2021-03-10 18:31 ` [PATCH 06/24] setnetgrent.3: " Alejandro Colomar
2021-03-10 18:31 ` [PATCH 07/24] sigwait.3: " Alejandro Colomar
2021-03-10 18:31 ` [PATCH 08/24] statvfs.3: " Alejandro Colomar
2021-03-10 18:31 ` [PATCH 09/24] stpcpy.3: " Alejandro Colomar
2021-03-10 18:31 ` [PATCH 10/24] stpncpy.3: " Alejandro Colomar
2021-03-10 18:31 ` [PATCH 11/24] strcat.3: " Alejandro Colomar
2021-03-10 18:31 ` [PATCH 12/24] strcpy.3: " Alejandro Colomar
2021-03-10 18:31 ` [PATCH 13/24] strfmon.3: " Alejandro Colomar
2021-03-10 18:31 ` [PATCH 14/24] strftime.3: " Alejandro Colomar
2021-03-10 18:31 ` [PATCH 15/24] string.3: " Alejandro Colomar
2021-03-10 18:31 ` [PATCH 16/24] " Alejandro Colomar
2021-03-10 18:31 ` [PATCH 17/24] strptime.3: " Alejandro Colomar
2021-03-10 18:31 ` [PATCH 18/24] strsep.3: " Alejandro Colomar
2021-03-10 18:31 ` [PATCH 19/24] strtod.3: " Alejandro Colomar
2021-03-10 18:31 ` [PATCH 20/24] strtoimax.3: " Alejandro Colomar
2021-03-10 18:31 ` [PATCH 21/24] strtok.3: " Alejandro Colomar
2021-03-10 18:31 ` [PATCH 22/24] strtol.3, strtoul.3: " Alejandro Colomar
2021-03-10 18:31 ` [PATCH 23/24] strxfrm.3: " Alejandro Colomar
2021-03-10 18:31 ` [PATCH 24/24] swab.3: " Alejandro Colomar
2021-03-14 20:51 ` [PATCH 00/24] man3: SYNOPSIS: Use 'restrict' in prototypes (batch 5) Michael Kerrisk (man-pages)
2021-03-14 20:53 ` Michael Kerrisk (man-pages)
2021-03-19 21:08 ` Alejandro Colomar (man-pages) [this message]
2021-03-19 20:59 ` Alejandro Colomar (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=c5b11775-bc89-7e89-33f9-1d56dc8fb92a@gmail.com \
--to=alx.manpages@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=xypron.glpk@gmx.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).