From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Community Patch Review Meeting: 2021-01-18 at 0900h EST (UTC-5)
Date: Mon, 18 Jan 2021 09:52:20 -0500 [thread overview]
Message-ID: <4ea555e2-f006-a848-1c4e-adcdad4054d7@redhat.com> (raw)
Forgot to send out meeting reminder :-)
Meeting: 2021-01-18 @ 0900h EST (UTC-5)
Video/Audio: https://jitsi.member.fsf.org/glibc-patch-review
IRC: #glibc on freenode.
Will review release blocker patches and desirable patches.
Notes:
Moved DSO sorting to glibc 2.34 to resolve issues with dual sorting transition.
Carlos to review _SC_MINSIGSTKSZ and deprecate _SC_SIGSTKSZ_SOURCE.
Florian to review COMMON_CPUID_INDEX_MAX handshake.
Florian to review Fix getdents64 fallback on mips64-n32
Fix static PIE ifunc resolvers.
Adhemerval to email HJ and Szabolcs on status.
Florian Weimer to ping Martin Sebor on PR/98512.
Florian to raise issue around check for x86 ISA v2 and v3 and virt.
What about deadlines for the release?
Keep only those issues that are ABI regressions.
How do we shorten the release window?
Discuss on libc-alpha with new thread topic.
--
Cheers,
Carlos.
next reply other threads:[~2021-01-18 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 14:52 Carlos O'Donell [this message]
2021-01-18 15:00 ` H.J. Lu
2021-01-18 15:33 ` Carlos O'Donell
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=4ea555e2-f006-a848-1c4e-adcdad4054d7@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).