From: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v2] <stdio.h>: Make fopencookie, vasprintf, asprintf available by default
Date: Thu, 06 Apr 2023 17:04:21 +0200 [thread overview]
Message-ID: <87cz4hm4qy.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <6c3d6c35-69e3-4d2b-2e91-011b160df37f@linaro.org> (Adhemerval Zanella Netto's message of "Thu, 8 Dec 2022 14:08:52 -0300")
* Adhemerval Zanella Netto:
> On 24/11/22 12:49, Florian Weimer via Libc-alpha wrote:
>> FreeBSD makes these functions available by default, so we should
>> not treat them as GNU-specific and restrict them to _GNU_SOURCE.
>>
>
>
> LGTM, thanks.
>
> Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Thanks. Pushed after retesting.
Florian
prev parent reply other threads:[~2023-04-06 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 15:49 [PATCH v2] <stdio.h>: Make fopencookie, vasprintf, asprintf available by default Florian Weimer via Libc-alpha
2022-12-08 17:08 ` Adhemerval Zanella Netto via Libc-alpha
2023-04-06 15:04 ` Florian Weimer via Libc-alpha [this message]
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cz4hm4qy.fsf@oldenburg.str.redhat.com \
--to=libc-alpha@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).