From: Arjun Shankar <arjun@redhat.com>
To: Carlos O'Donell <codonell@redhat.com>,
Siddhesh Poyarekar <siddhesh@gotplt.org>,
GLIBC Devel <libc-alpha@sourceware.org>,
Chung-Lin Tang <cltang@codesourcery.com>
Subject: Re: 2.31: < 2 weeks to go
Date: Fri, 20 Dec 2019 10:45:27 +0100 [thread overview]
Message-ID: <189c243e9e1e144a6660f5a5ed991a1978839482.camel@redhat.com> (raw)
In-Reply-To: <3ba1511a-94ac-6b43-0288-1ef157796fba@redhat.com>
> On 12/19/19 10:35 PM, Siddhesh Poyarekar wrote:
> > Less than two weeks to go for 2.31 freeze. I intend to announce a
> > freeze on 31st December around afternoon IST. Here's a reminder that if
> > you'd like your patchset considered for inclusion during the freeze, it
> > needs to be in the blockers list on the release page[1]. Please cc me
> > in patch pings if you haven't been able to get reviews and need
> > attention.
> > [1] https://sourceware.org/glibc/wiki/Release/2.31
On Thu, 2019-12-19 at 22:56 -0500, Carlos O'Donell wrote:
> Arjun,
>
> I think your gconv cleanup should go on this list. We've been reviewing
> this code internally and externally and it really helps with the converter
> hangs.
>
> I'll look at reviewing this after I get done the Mentor Graphics review
> for ld.so sorting.
I added an entry for the iconv option parsing rewrite to the list of
blockers. I have a v2 coming up, hopefully today.
Cheers,
Arjun
next prev parent reply other threads:[~2019-12-20 9:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 3:35 2.31: < 2 weeks to go Siddhesh Poyarekar
2019-12-20 3:56 ` Carlos O'Donell
2019-12-20 9:45 ` Arjun Shankar [this message]
2019-12-24 14:36 ` Chung-Lin Tang
2019-12-27 12:39 ` Carlos O'Donell
2020-01-07 19:29 ` Carlos O'Donell
2019-12-20 14:30 ` Florian Weimer
2019-12-22 17:38 ` Siddhesh Poyarekar
2019-12-22 18:59 ` Joseph Myers
2019-12-30 12:20 ` Siddhesh Poyarekar
2019-12-30 15:00 ` Florian Weimer
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=189c243e9e1e144a6660f5a5ed991a1978839482.camel@redhat.com \
--to=arjun@redhat.com \
--cc=cltang@codesourcery.com \
--cc=codonell@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@gotplt.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).