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 18:34:00 +0000 (UTC) [thread overview]
Message-ID: <0c071aeb-14f4-cd62-8fab-f3eb2659f77b@redhat.com> (raw)
In-Reply-To: <CALvbMcB=jvi0JUwK=bZGdPGEGGtcPXHyrT0Ru1wwTqUWB6FV3Q@mail.gmail.com>
On Mon, 21 Sep 2026, Andrea Pinski wrote:
> > * Discuss on libc-alpha finalize mailing list names:
> > * Place mailing list services under lists.glibc.coretoolchain.dev
> > * glibc-announce@lists.glibc.coretoolchain.dev
> > * glibc-devel@lists.glibc.coretoolchain.dev
> > * glibc-stable@lists.glibc.coretoolchain.dev
> > * glibc-testresults@lists.glibc.coretoolchain.dev
> > * glibc-help@glibc.lists.glibc.coretoolchain.dev
> > * glibc-vcs@lists.glibc.coretoolchain.dev
>
> Especially here about why not just have lists.coretoolchain.dev rather
> than have a glibc subdomain. Plus isn't glibc on the mailing list
> name and the domain redundant?
The subdomain facilitates different projects making different hosting
choices in future (via DNS changes) if they wish without needing to make
further changes to email addresses.
The use of glibc in the list names is formally redundant, but we felt it
was convenient for informal references to the lists in text, email client
aliases, etc. to be able to talk about e.g. glibc-devel and have it
unambiguous rather than just talking about devel@ which could refer to
multiple projects.
--
Joseph S. Myers
josmyers@redhat.com
next prev parent reply other threads:[~2026-09-22 18:34 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 [this message]
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
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=0c071aeb-14f4-cd62-8fab-f3eb2659f77b@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