From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>,
DJ Delorie <dj@redhat.com>,
Siddhesh Poyarekar <siddhesh@redhat.com>
Subject: Re: Monday Patch Queue Review update (2022-08-29)
Date: Fri, 2 Sep 2022 22:21:19 -0400 [thread overview]
Message-ID: <6847c0e8-dd3e-a9a2-78bc-4b1dccfaa096@redhat.com> (raw)
In-Reply-To: <e6d8e358-4731-a56f-464c-e00c95ca58f4@redhat.com>
On 9/1/22 16:34, Carlos O'Donell wrote:
> Most recent meeting status is always here:
> https://sourceware.org/glibc/wiki/PatchworkReviewMeetings#Update
>
> Meeting: 2022-08-29 @ 0900h EST5EDT
>
> Video/Audio: https://bluejeans.com/9093064454
>
> IRC: #glibc on OFTC.
>
> Review new patches and attendee requested reviews.
>
> * State NEW delegate NOBODY is at 233
> * Start at 57139.
> * Noted that Sourcware.org was is slow today and having connection issues.
> * Carlos to check with overseers.
> * syslog: Fix large messages (BZ#29536) (Adhemerval)
> * New for 2.36.
> * Carlos to ask DJ for review.
... and my apologies to DJ since I didn't get around to asking him, and this
patch got reviewed by Siddhesh who was already doing the security review.
Thank you Siddhesh!
> * Asked Sidddhesh to review security +/-
> * Rework exception handling in the dynamic loader [BZ #25486] (Florian)
> * Ask Szabolcs or Carlos for review.
> * elf: Call __libc_early_init for reused namespaces (bug 29528) (Florian)
> * v2 already committed. Superseded.
> * nss_dns: Fix handling of non-host CNAMEs (bug 12154) (Florian)
> * Reviewed by Siddhesh. Two patches remaining.
> * Stopped 57078
> * [v4] elf: Remove -fno-tree-loop-distribute-patterns usage on dl-support (Adhemerval)
> * [v3] debug: test for more required cacellation points (BZ# 29274) (Adhemerval)
> * Carlos to review.
>
--
Cheers,
Carlos.
prev parent reply other threads:[~2022-09-03 2:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 20:34 Carlos O'Donell
2022-09-03 2:21 ` Carlos O'Donell [this message]
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=6847c0e8-dd3e-a9a2-78bc-4b1dccfaa096@redhat.com \
--to=carlos@redhat.com \
--cc=dj@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@redhat.com \
/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).