From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v4 4/5] io: Add closefrom [BZ #10353]
Date: Thu, 11 Mar 2021 08:24:23 -0300 [thread overview]
Message-ID: <9105b5b4-6609-b72c-d2ce-09c6bad980eb@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2103102154090.797684@digraph.polyomino.org.uk>
On 10/03/2021 18:54, Joseph Myers wrote:
> On Wed, 10 Mar 2021, Adhemerval Zanella via Libc-alpha wrote:
>
>> diff --git a/NEWS b/NEWS
>> index ff2b952a06..0c7bc74cca 100644
>> --- a/NEWS
>> +++ b/NEWS
>> @@ -91,6 +91,10 @@ Major new features:
>> The latest GCC available at this time (10.2) does not support this level of
>> fortification.
>>
>> +* The function closefrom has been added. It closes all file descriptors
>> + greater than given integer. This function is a GNU extension, although it
>> + also present in other systems.
>
> That's the NEWS section for 2.33. This needs to go in the section for
> 2.34.
>
Ack.
next prev parent reply other threads:[~2021-03-11 11:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 15:26 [PATCH v4 1/5] support: Add support_stack_alloc Adhemerval Zanella
2021-03-10 15:26 ` [PATCH v4 2/5] support: Add xclone Adhemerval Zanella
2021-03-10 15:26 ` [PATCH v4 3/5] Linux: Add close_range Adhemerval Zanella
2021-03-24 22:42 ` Alyssa Ross
2021-03-10 15:26 ` [PATCH v4 4/5] io: Add closefrom [BZ #10353] Adhemerval Zanella
2021-03-10 21:54 ` Joseph Myers
2021-03-11 11:24 ` Adhemerval Zanella [this message]
2021-03-10 15:26 ` [PATCH v4 5/5] posix: Add posix_spawn_file_actions_closefrom_np Adhemerval Zanella
2021-03-10 16:10 ` [PATCH v4 1/5] support: Add support_stack_alloc Florian Weimer
2021-03-12 13:24 ` Adhemerval Zanella
2021-03-12 13:35 ` Florian Weimer
2021-03-12 14:01 ` Adhemerval Zanella
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=9105b5b4-6609-b72c-d2ce-09c6bad980eb@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).