From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Monday Patch Queue Review update (2024-04-22)
Date: Mon, 22 Apr 2024 09:35:21 -0400 [thread overview]
Message-ID: <8b4958b8-c323-4013-aff7-9785344dbe38@redhat.com> (raw)
Most recent meeting status is always here:
https://sourceware.org/glibc/wiki/PatchworkReviewMeetings#Update
Meeting: 2024-04-22 @ 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 363.
* Carlos's SLI at 340 days average patch age in queue and 124967 accumulated patch days.
* Starting patch queue at 88833
* Discussed CVE-2024-2961
* Adhemerval: Note that Aurelien backported to release/2.31/master
* Carlos: Is this because Debian 11 uses 2.31?
* Simon: Yes, debian 11 uses 2.31.
* Open action item to discuss with Debian (Aurelien) the state of release/2.31/master
* Simon: I want to ship what is in 2.31 in Ubuntu 20.04, but need to convince the teams.
* Florian: The backport expectations get harder as you need more branches getting the fixes.
* Simon: I have a response for why they wouldn't want us to track the release branch.
* Florian: Small test case fix posted for tst-cancel7.c fix, hopefully get a review.
* Backport the fixes for time64_t into the rolling release branches.
* Backport until 2.34 which is the first release with time64_t support across all arches.
* Florian: Is there a debian-devel equivalent?
* Simon: Yes, ubuntu-devel, moderated though.
* Noted that sourceware.org is down for the hardware upgrade so no patch review.
--
Cheers,
Carlos.
reply other threads:[~2024-04-22 15:49 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
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=8b4958b8-c323-4013-aff7-9785344dbe38@redhat.com \
--to=carlos@redhat.com \
--cc=libc-alpha@sourceware.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).