unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
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: Fri, 27 Dec 2019 07:39:12 -0500	[thread overview]
Message-ID: <529a33e9-8e29-4c8c-3354-692016f015f2@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.

Just posted my review notes:
https://www.sourceware.org/ml/libc-alpha/2019-12/msg00753.html

Thank you for your patience.

-- 
Cheers,
Carlos.


  reply	other threads:[~2019-12-27 12:39 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 [this message]
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=529a33e9-8e29-4c8c-3354-692016f015f2@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).