From: Carlos O'Donell via Gdb <gdb@sourceware.org>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>,
Andrea Pinski <andrew.pinski@oss.qualcomm.com>,
Joseph Myers <josmyers@redhat.com>
Cc: gcc developers <gcc@gcc.gnu.org>,
glibc developers <libc-alpha@sourceware.org>,
gdb developers <gdb@sourceware.org>,
binutils developers <binutils@sourceware.org>
Subject: Re: Meeting Minutes - Office Hours for CTI - 2026-09-18
Date: Fri, 25 Sep 2026 17:28:40 -0400 [thread overview]
Message-ID: <d214d414-7658-4c10-b49c-86066b5c4d53@redhat.com> (raw)
In-Reply-To: <043b5970-6211-41cc-a6bd-2cbf017e5b64@gotplt.org>
On 9/24/26 11:15 AM, Siddhesh Poyarekar wrote:
> On 2026-09-22 15:02, Andrea Pinski wrote:
>> Also why NOT just one email list? Why 6 mailing lists? What is the
>> need for glibc-stable?
>
> DJ already answered this; glibc-stable is actively used by downstream
> developers. I won't object if there's consensus towards folding it
> into libc-alpha, but that would mean dozens of additional (likely
> irrelevant for others) messages on the list. That said though, I do
> like the idea of the original patch and backports all living in the
> same list, ideally with a `References` tag linking them up since that
> would make processing them so much easier, especially for security
> fixes.
We had an on-list discussion *specifically* about this topic in May 2026.
"[RFC] How many mailing lists does glibc need or use? Closing 4 lists."
https://inbox.sourceware.org/libc-alpha/932cc126-4a9a-4507-9c26-2c13524100d0@redhat.com/
I received feedback from Collin, and Arjun.
Then again to discuss closing some lists:
"[RFC] Closing libc-locales and glibc-bugs-regex mailing lists at the end of June 2026."
https://inbox.sourceware.org/libc-alpha/91482a3d-3abb-469e-9616-da83559f7e6a@redhat.com/
(which still need to be closed, TODO item for me).
--
Cheers,
Carlos.
prev parent reply other threads:[~2026-09-25 21:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 16:32 Carlos O'Donell via Gdb
2026-09-21 16:55 ` Andrea Pinski via Gdb
2026-09-21 17:58 ` DJ Delorie via Gdb
2026-09-22 18:14 ` Siddhesh Poyarekar
2026-09-22 9:46 ` Mark Wielaard
2026-09-22 18:34 ` Joseph Myers via Gdb
2026-09-22 19:02 ` Andrea Pinski via Gdb
2026-09-22 19:14 ` DJ Delorie via Gdb
2026-09-22 19:22 ` Andrea Pinski via Gdb
2026-09-24 14:55 ` Siddhesh Poyarekar
2026-09-22 20:37 ` Joseph Myers via Gdb
2026-09-23 15:58 ` Mark Wielaard
2026-09-24 15:15 ` Siddhesh Poyarekar
2026-09-24 15:21 ` Siddhesh Poyarekar
2026-09-25 21:28 ` Carlos O'Donell via Gdb [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=d214d414-7658-4c10-b49c-86066b5c4d53@redhat.com \
--to=gdb@sourceware.org \
--cc=andrew.pinski@oss.qualcomm.com \
--cc=binutils@sourceware.org \
--cc=carlos@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=josmyers@redhat.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