From: Joseph Myers via Gdb <gdb@sourceware.org>
To: Andrea Pinski <andrew.pinski@oss.qualcomm.com>
Cc: Carlos O'Donell <carlos@redhat.com>,
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: Tue, 22 Sep 2026 20:37:46 +0000 (UTC) [thread overview]
Message-ID: <2359b616-44b8-742b-dfee-fcecf516d709@redhat.com> (raw)
In-Reply-To: <CALvbMcD1hbbWqCG5kBZ7JKiPJabMgXtSfBwXNsjs6wkYKnDJxg@mail.gmail.com>
On Tue, 22 Sep 2026, Andrea Pinski wrote:
> So there was no consensus on the community members except for the ones
> who were at the meeting?
It makes a lot more sense to work out a coherent list of mailing list
names (this is about the names, the actual set of lists has already been
discussed on libc-alpha based on a proposal we made at an earlier stage)
in a small group rather than bikeshedding naming in a long thread on a
large mailing list.
> Also why NOT use a forge for patches instead of pushing for mailing lists?
There are plenty of uses for discussions not associated with a particular
patch. A forge might be a replacement for patchwork, but not for mailing
lists.
> Also why NOT just one email list? Why 6 mailing lists?
> What is the need for glibc-stable?
We already discussed the set of mailing lists on libc-alpha in May / June.
Based on that discussion, we concluded that libc-stable was of use
separately from the main development list, but that libc-locales and
glibc-bugs-regex should be closed. There was a further opportunity for
discussion of the closure of those two lists, which I don't think saw any
objections.
--
Joseph S. Myers
josmyers@redhat.com
next prev parent reply other threads:[~2026-09-22 20:38 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 [this message]
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
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=2359b616-44b8-742b-dfee-fcecf516d709@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 \
/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