From: Mark Wielaard <mark@klomp.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: Wed, 23 Sep 2026 17:58:44 +0200 [thread overview]
Message-ID: <e5dc112a7abd46a5988025241f4a2fef98fb94b1.camel@klomp.org> (raw)
In-Reply-To: <CALvbMcD1hbbWqCG5kBZ7JKiPJabMgXtSfBwXNsjs6wkYKnDJxg@mail.gmail.com>
Hi Andrea,
On Tue, 2026-09-22 at 12:02 -0700, Andrea Pinski via Gdb wrote:
> So there was no consensus on the community members except for the ones
> who were at the meeting?
> Ok. I think that it is wrong to have separate domains. The moving
> part is a bad reason for having a seperate domain. If we have a
> separate domain the redundant part is just broken and maybe better
> names could come up with.
>
> Also why NOT use a forge for patches instead of pushing for mailing lists?
> Also why NOT just one email list? Why 6 mailing lists?
> What is the need for glibc-stable?
> Maybe glibc-testresults should not be a mailing list but rather a
> better way of collecting test results and displaying them?
I think I understand your point, but I think you are not expressing it
very clearly because these questions are phrased rhetorically or
sarcastically (at least that is how they read to me). Now people are
just answering your questions as if they are part of the disputed
proposal.
But all of these questions can (and should) be decided separately.
glibc is already setup on the forge https://forge.sourceware.org/glibc
Currently it is only used as stable mirror. But if someone wants to
experiment with merge requests we can install some of the bots/tools
gcc has been using. If any list should be closed, archived,
renamed/split we can easily do that, no need to move infrastructure.
glibc buildbot results are already going into bunsen
https://builder.sourceware.org/testruns/ connecting patchwork and
buildbot is a work in progress.
Cheers,
Mark
next prev parent reply other threads:[~2026-09-23 15:59 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
2026-09-23 15:58 ` Mark Wielaard [this message]
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=e5dc112a7abd46a5988025241f4a2fef98fb94b1.camel@klomp.org \
--to=mark@klomp.org \
--cc=andrew.pinski@oss.qualcomm.com \
--cc=binutils@sourceware.org \
--cc=carlos@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.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