From: Alejandro Colomar <alx@kernel.org>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v3] stdio.3: note down fmemopen(3), fopencookie(3), and open_[w]memstream(3)
Date: Thu, 28 Dec 2023 21:10:15 +0100 [thread overview]
Message-ID: <ZY3WJ0UOM4nPEsQZ@debian> (raw)
In-Reply-To: <sbwbc5fmppc77kqnzjmvxl57ke76lqoagn4c3o7chezt5b4rzd@tarta.nabijaczleweli.xyz>
[-- Attachment #1: Type: text/plain, Size: 999 bytes --]
On Thu, Dec 28, 2023 at 08:28:22PM +0100, наб wrote:
> On Thu, Dec 28, 2023 at 08:06:14PM +0100, Alejandro Colomar wrote:
> > On Tue, Dec 26, 2023 at 05:03:37PM +0100, наб wrote:
> > Why use opening here, but open everywhere else?
> These are the NAMEs verbatim, like the fopen entry:
Makes sense. Would you mind fixing the NAMEs too in another patch? :-)
Cheers,
Alex
> $ grep -A1 NAME man3/{fopen,fopencookie,fmemopen,open_memstream}.3
> man3/fopen.3:.SH NAME
> man3/fopen.3-fopen, fdopen, freopen \- stream open functions
> --
> man3/fopencookie.3:.SH NAME
> man3/fopencookie.3-fopencookie \- opening a custom stream
> --
> man3/fmemopen.3:.SH NAME
> man3/fmemopen.3-fmemopen \- open memory as stream
> --
> man3/open_memstream.3:.SH NAME
> man3/open_memstream.3-open_memstream, open_wmemstream \- open a dynamic memory buffer stream
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-12-28 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-26 15:31 [PATCH] stdio.3: note down fmemopen(3) and fopencookie(3) наб
2023-12-26 16:02 ` [PATCH v2] stdio.3: note down fmemopen(3), fopencookie(3), and open_[w]memstream(3) наб
2023-12-26 16:03 ` [PATCH v3] " наб
2023-12-28 19:06 ` Alejandro Colomar
2023-12-28 19:28 ` наб
2023-12-28 20:10 ` Alejandro Colomar [this message]
2023-12-29 13:39 ` [PATCH] fopencookie.3, stdio.3: wfix наб
2023-12-29 13:52 ` Alejandro Colomar
2023-12-28 20:14 ` [PATCH v3] stdio.3: note down fmemopen(3), fopencookie(3), and open_[w]memstream(3) Alejandro Colomar
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=ZY3WJ0UOM4nPEsQZ@debian \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
/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