Re: Proposed updates to the gcc forge repositories
Claudio Bantaloukas <[email protected]> Thu, 16 Jul 2026 10:25:13 +0100
| Newsgroups | gmane.comp.ai.sourceware.forge,gmane.comp.gcc.devel |
|---|---|
| Message-ID | <[email protected]> |
On 11/07/2026 06:45, Basile STARYNKEVITCH wrote: > On Fri, Jul 10, 2026 at 8:25 AM Claudio Bantaloukas via Gcc > <[email protected]> wrote: >> >>> I plan on: >>> - Renaming gcc/gcc-TEST to gcc/gcc (to make it clear it's a bit >> less of >>> a test) > > > I think that renaming is extremely confusing. Not being a native > English speaker I dare not suggest anything better. Hopefully it helps that now we have: - https://forge.sourceware.org/gcc as a gcc team container - https://forge.sourceware.org/gcc/gcc for the main repository - https://forge.sourceware.org/gcc/gcc-wwwdocs for the gcc website - https://forge.sourceware.org/gcc/gcc-archive as an archive of all branches currently on gcc.gnu.org/gcc.git - https://forge.sourceware.org/gcc/gcc-wwwdocs-archive as a pure mirror of the gcc.gnu.org/gcc-wwwdocs.git repository - https://forge.sourceware.org/gcc/gcc-a68 as an archive of the effort to upstream algol68 As Sam suggests, it's a way to structure things that is widely used. Thinking about this more, I'm convinced https://forge.sourceware.org/gcc/gcc-wwwdocs-archive is not needed. There's only one branch and that is mirrored on https://forge.sourceware.org/gcc/gcc-wwwdocs by the bot. https://forge.sourceware.org/gcc/gcc-a68 is another thing to address. I had a chat with Jose and apparently the gcc-15-a68 branch, visible on https://forge.sourceware.org/gcc/gcc-a68/src/branch/releases/gcc-15-a68 is currently used by the debian team as a source for their gcc-a68-15 package. See https://salsa.debian.org/toolchain-team/gcc/-/commit/4437a49111b4a56154b4bda14cc8ad92b476830d where this is mentioned. I think what we should do is import the releases/gcc-15-a68 branch in sourceware proper and archive the https://forge.sourceware.org/gcc/gcc-a68 repository now that it has served its purpose. To summarize: - remove gcc/gcc-wwwdocs-archive - push releases/gcc-15-a68 from the gcc/gcc-a68 repo to the main gcc repository in sourceware - unlink and archive gcc/gcc-a68 on forge Thoughts? > Regards