From: Carlos O'Donell via Gdb <gdb@sourceware.org>
To: glibc developers <libc-alpha@sourceware.org>,
gdb developers <gdb@sourceware.org>,
gcc developers <gcc@gcc.gnu.org>,
binutils developers <binutils@sourceware.org>
Subject: Meeting Minutes - Office Hours for CTI - 2026-11-06
Date: Sat, 7 Nov 2026 12:22:23 -0500 [thread overview]
Message-ID: <cb344335-9a53-4f85-8472-8264f602dffb@redhat.com> (raw)
CTI: https://cti.coretoolchain.dev/
The CTI project holds Office Hours every Friday, these are the minutes for this Friday's meeting.
The CTI project in collaboration with glibc is working on: https://cti.coretoolchain.dev/projects/glibc.html
RFCs:
[RFC] Using bugspray for updating glibc bugs in bugzilla?
https://inbox.sourceware.org/libc-alpha/a1c0fb87-de0f-40da-a917-25520839d209@redhat.com/
[RFC] Using git-mailbomb as post-commit VCS to email system for glibc-cvs emails?
https://inbox.sourceware.org/libc-alpha/5d2ef95d-94c4-40aa-83a7-84dc5f376e2b@redhat.com/
[RFC] Using project and service specific DNS end points to support flexible deployments.
https://inbox.sourceware.org/libc-alpha/8e167d49-86c5-45ba-841d-f9f74151d596@redhat.com/T/#u
[RFC] Provide horizontally scaled git pull mirrors for the GNU Toolchain, starting with glibc.
https://inbox.sourceware.org/libc-alpha/272e308a-a703-4824-b823-cd8e5266f00b@redhat.com/
Posting across the project mailing lists since some developers have questions and are only subscribed on some lists.
Agenda:
* Carlos: Note from Siddhesh that he's working on the wiki RFC, but is out next week and expets to post this Nov 16-20 week.
* Carlos: I'm still working on verifying Sachin's regexps in my ansible playbook with VM.
* Discussed DJ's comment about ingress server scaling and service and project specific end points.
* Noted that this is distinct from and can be implemented in addition to the DNS changes suggested by the RFC.
--
Cheers,
Carlos.
reply other threads:[~2026-11-07 17:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=cb344335-9a53-4f85-8472-8264f602dffb@redhat.com \
--to=gdb@sourceware.org \
--cc=binutils@sourceware.org \
--cc=carlos@redhat.com \
--cc=gcc@gcc.gnu.org \
--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