From: Florian Weimer <fweimer@redhat.com>
To: Nix <nix@esperi.org.uk>, "Carlos O'Donell" <carlos@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: glibc 2.25 development --- 46 days to freeze.
Date: Tue, 22 Nov 2016 18:58:00 -0000 [thread overview]
Message-ID: <e675edb1-cc23-51c7-7098-458f7781ae65@redhat.com> (raw)
In-Reply-To: <87mvgtu1ns.fsf@esperi.org.uk>
On 11/21/2016 01:17 AM, Nix wrote:
> On 15 Nov 2016, Carlos O'Donell told this:
>
>> Community,
>>
>> We have 46 days of active development until the freeze for glibc 2.25 starts.
>>
>> We have 77 days until the release of glibc 2.25.
>>
>> Make the most of it :-)
>
> FWIW I'll be posting a new stack-protector series (rebased atop the
> ifunc changes, as requested) as soon as its tests pass.
I'll happy to re-review them.
Thanks,
Florian
next prev parent reply other threads:[~2016-11-22 18:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 20:55 Carlos O'Donell
2016-11-16 5:57 ` Jochen Hein
2016-11-20 4:40 ` Siddhesh Poyarekar
2016-11-20 6:11 ` Jochen Hein
2016-11-20 11:34 ` Benno Schulenberg
2016-11-20 13:08 ` Siddhesh Poyarekar
2016-12-01 13:32 ` Siddhesh Poyarekar
2016-12-01 16:03 ` Joseph Myers
2016-12-02 15:53 ` Carlos O'Donell
2016-12-02 15:57 ` Joseph Myers
2016-12-02 16:15 ` Carlos O'Donell
2016-12-02 15:54 ` Carlos O'Donell
2016-12-02 18:16 ` Siddhesh Poyarekar
2016-12-19 23:06 ` Carlos O'Donell
2016-12-20 16:54 ` Siddhesh Poyarekar
2016-12-02 18:18 ` Siddhesh Poyarekar
2016-12-19 14:24 ` Carlos O'Donell
2016-12-16 22:56 ` Mike Frysinger
2016-12-17 5:24 ` Siddhesh Poyarekar
2016-11-21 0:17 ` Nix
2016-11-22 18:58 ` Florian Weimer [this message]
2016-12-17 15:13 ` Zack Weinberg
2016-12-19 13:58 ` Carlos O'Donell
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=e675edb1-cc23-51c7-7098-458f7781ae65@redhat.com \
--to=fweimer@redhat.com \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=nix@esperi.org.uk \
/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).