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
