From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <colomar.6.4.3@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
libc-alpha@sourceware.org, g.branden.robinson@gmail.com
Subject: Re: [PATCH v2 2/3] system_data_types.7: Add 'FILE'
Date: Tue, 29 Sep 2020 15:35:32 +0200 [thread overview]
Message-ID: <8f408cee-2a52-027e-3912-c6ba4b0b9708@gmail.com> (raw)
In-Reply-To: <0a5ee9a4-8787-5bce-92bb-a2ae10eaed54@gmail.com>
On 9/29/20 3:15 PM, Alejandro Colomar wrote:
> Hi Michael,
>
> Ping -c2 :)
>
> patches 2/3 and 3/3 of this set are pending,
> the patch which was holding them has already been applied,
> and should have no conflicts in the current HEAD (tell me if otherwise).
Thanks for the prod! Those two patches are applied and pushed.
Thanks,
Michael
> On 2020-09-28 11:06, Alejandro Colomar wrote:
>> Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
>> ---
>> man7/system_data_types.7 | 23 +++++++++++++++++++++++
>> 1 file changed, 23 insertions(+)
>>
>> Hi Michael,
>>
>> Please hold until the ffix is applied (or not).
>>
>> Thanks,
>>
>> Alex
>>
>> diff --git a/man7/system_data_types.7 b/man7/system_data_types.7
>> index ff0403df9..16930985e 100644
>> --- a/man7/system_data_types.7
>> +++ b/man7/system_data_types.7
>> @@ -197,6 +197,29 @@ Conforming to: C99 and later; POSIX.1-2001 and later.
>> See also:
>> .BR fenv (3)
>> .RE
>> +.\"------------------------------------- FILE -------------------------/
>> +.TP
>> +.I FILE
>> +.RS
>> +.br
>> +Include:
>> +.IR <stdio.h> ;
>> +or
>> +.IR <wchar.h> .
>> +.PP
>> +An object type used for streams.
>> +.PP
>> +Conforming to: C99 and later; POSIX.1-2001 and later.
>> +.PP
>> +See also:
>> +.BR fclose (3),
>> +.BR flockfile (3),
>> +.BR fopen (3),
>> +.BR fprintf (3),
>> +.BR fread (3),
>> +.BR fscanf (3),
>> +.BR stdin (3),
>> +.BR stdio (3)
>> +.RE
>> .\"------------------------------------- float_t ----------------------/
>> .TP
>> .I float_t
>>
--
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:[~2020-09-29 13:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 21:13 [PATCH 1/3] system_data_types.7: ffix Alejandro Colomar
2020-09-27 21:13 ` [PATCH 2/3] system_data_types.7: Add 'FILE' Alejandro Colomar
2020-09-28 6:04 ` Michael Kerrisk (man-pages)
2020-09-28 9:06 ` [PATCH v2 " Alejandro Colomar
2020-09-29 13:15 ` Alejandro Colomar
2020-09-29 13:35 ` Michael Kerrisk (man-pages) [this message]
2020-09-27 21:13 ` [PATCH 3/3] FILE.3: New link to system_data_types(7) Alejandro Colomar
2020-09-28 5:59 ` [PATCH 1/3] system_data_types.7: ffix Michael Kerrisk (man-pages)
2020-09-28 9:03 ` [PATCH v2 " Alejandro Colomar
2020-09-28 10:34 ` Michael Kerrisk (man-pages)
2020-09-28 10:37 ` Alejandro Colomar
2020-09-28 11:13 ` G. Branden Robinson
2020-09-28 13:06 ` G. Branden Robinson
2020-09-28 13:44 ` Alejandro Colomar
2020-09-30 10:43 ` G. Branden Robinson
2020-09-30 21:32 ` Alejandro Colomar
2020-10-01 7:37 ` Michael Kerrisk (man-pages)
2020-10-01 7:52 ` Alejandro Colomar
2020-10-01 9:36 ` Michael Kerrisk (man-pages)
2020-09-28 10:40 ` [PATCH " G. Branden Robinson
2020-09-28 10:51 ` Alejandro Colomar
2020-09-28 12:49 ` G. Branden Robinson
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=8f408cee-2a52-027e-3912-c6ba4b0b9708@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=colomar.6.4.3@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=libc-alpha@sourceware.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox