From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Andrea Pinski <andrew.pinski@oss.qualcomm.com>,
DJ Delorie <dj@redhat.com>
Cc: Joseph Myers <josmyers@redhat.com>,
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: Thu, 24 Sep 2026 10:55:30 -0400 [thread overview]
Message-ID: <f833cd95-14ba-4702-a845-c91695eb7703@gotplt.org> (raw)
In-Reply-To: <CALvbMcAupz_NUD_wSYaZP_yXs5TtLgJ1Y1MztWyy3nF=LS0v6Q@mail.gmail.com>
On 2026-09-22 15:22, Andrea Pinski wrote:
>>> What is the need for glibc-stable?
>>
>> Downstream maintainers who need to watch for bugfixes. I would hope
>> by now everyone would know this.
>
> Why not just use -announcement for that?
-announce has a completely different audience and has very low volume.
It is limited to significant events, like release announcements and
security advisory announcements.
Sid
next prev parent reply other threads:[~2026-09-24 14:56 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 [this message]
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=f833cd95-14ba-4702-a845-c91695eb7703@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=andrew.pinski@oss.qualcomm.com \
--cc=binutils@sourceware.org \
--cc=carlos@redhat.com \
--cc=dj@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.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