From: Carlos O'Donell <codonell@redhat.com>
To: cltang@codesourcery.com, Siddhesh Poyarekar <siddhesh@gotplt.org>,
GLIBC Devel <libc-alpha@sourceware.org>,
Arjun Shankar <ashankar@redhat.com>
Subject: Re: 2.31: < 2 weeks to go
Date: Tue, 7 Jan 2020 14:29:14 -0500 [thread overview]
Message-ID: <389ff45e-04cf-dd17-3400-1d6f412e920f@redhat.com> (raw)
In-Reply-To: <31d7e687-c427-6226-e40c-04561651786e@mentor.com>
On 12/24/19 9:36 AM, Chung-Lin Tang wrote:
> On 2019/12/20 12:56 PM, Carlos O'Donell wrote:
>> Chung-Lin,
>>
>> I suggest you also put the dynamic loader improvements on the blocker
>> list. I've been look at these for months, and I haven't found anything
>> really wrong with them. I need to post my review writeup, but I keep
>> getting blocked. I'm going to do that either tomorrow or next week.
>
> Thanks! I just added it to the 2.31 release Wiki page.
I finished my review, but in hindsight I've seen at least one odd
sorting which worries me, and so I think we need to move this to early
2.32. We should keep moving the review forward and aim to commit early
in February. This gives us the biggest window for finding problems.
In summary:
- Move ld.so improvements to 2.32.
- Aim to commit them in February.
Chung-Lin,
Would you like to split up the work a bit? I could take a look at
expanding the python syntax?
--
Cheers,
Carlos.
next prev parent reply other threads:[~2020-01-07 19:29 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
2019-12-24 14:36 ` Chung-Lin Tang
2019-12-27 12:39 ` Carlos O'Donell
2020-01-07 19:29 ` Carlos O'Donell [this message]
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=389ff45e-04cf-dd17-3400-1d6f412e920f@redhat.com \
--to=codonell@redhat.com \
--cc=ashankar@redhat.com \
--cc=cltang@codesourcery.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).