From: Carlos O'Donell via Gdb <gdb@sourceware.org>
To: gcc developers <gcc@gcc.gnu.org>,
glibc developers <libc-alpha@sourceware.org>,
gdb developers <gdb@sourceware.org>,
binutils developers <binutils@sourceware.org>
Subject: Meeting Minutes - Office Hours for CTI - 2026-09-18
Date: Mon, 21 Sep 2026 12:32:28 -0400 [thread overview]
Message-ID: <bd2ff3e3-29f8-4889-91bd-b62b02ffafb0@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
Posting across the project mailing lists since some developers had questions and are only subscribed on some lists.
Agenda:
* Community items that need review.
* 1. What does the ouput of vcs to email look like? Post to libc-alpha for review.
* What does the output of git-mailbomb-cron look like.
* Asked LF IT on #cti-help for examples of output.
* 2. What does the output of bug text to bugzilla look like? Post to libc-alpha for review.
* Asked LF IT on #cti-help for examples of output.
* Come up with exact DNS names for services that can be split and moved.
* Support using DNS to route services in the future and for isolation.
* Even though isolation can be achieved at the proxy side after DNS, the splitting is easier with DNS.
* Discuss on libc-alpha finalizing git URLs
* git.glibc.coretoolchain.dev/glibc (RO mirror)
* gitolite.glibc.coretoolchain.dev/glibc (RW for developers)
* gitolite.glibc.coretoolchain.dev/glibc-keyring (RW for admins)
* 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
* ACTION: Carlos to email the mailing list with proposals for discussion.
--
Cheers,
Carlos.
next reply other threads:[~2026-09-21 16:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 16:32 Carlos O'Donell via Gdb [this message]
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
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=bd2ff3e3-29f8-4889-91bd-b62b02ffafb0@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