From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>,
Michael Hudson-Doyle <michael.hudson@canonical.com>,
"Andreas K. Huettel" <dilfridge@gentoo.org>,
Andreas Schwab <schwab@suse.de>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Monday Patch Queue Review update (2023-09-18)
Date: Mon, 18 Sep 2023 09:45:09 -0400 [thread overview]
Message-ID: <3a5d3f8a-4a06-af69-93af-0a059ef9f67c@redhat.com> (raw)
Most recent meeting status is always here:
https://sourceware.org/glibc/wiki/PatchworkReviewMeetings#Update
Meeting: 2023-09-18 @ 0900h EST5EDT
Video/Audio: https://bbb.linuxfoundation.org/room/adm-alk-1uu-7fu
IRC: #glibc on OFTC.
Review new patches and restart review at the top.
* State NEW delegate NOBODY at 459 patches.
* Carlos's SLI at 185 days average patch age in queue and 86486 accumulated patch days.
* Review today is focused on the status of upcoming CVEs and distribution rebuilds.
* CVE-2023-4527: no-aaaa (Moderate impact)
* CVE-2023-4806: getaddrinfo (Moderate impact)
* CVE-2023-4813: gaih_inet (Moderate impact)
--
Cheers,
Carlos.
reply other threads:[~2023-09-18 13:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3a5d3f8a-4a06-af69-93af-0a059ef9f67c@redhat.com \
--to=carlos@redhat.com \
--cc=aurelien@aurel32.net \
--cc=dilfridge@gentoo.org \
--cc=libc-alpha@sourceware.org \
--cc=michael.hudson@canonical.com \
--cc=schwab@suse.de \
/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).