On Thu, Oct 24, 2024 at 1:25 PM Andrew Pinski <pins...@gmail.com> wrote: > > On Sun, Oct 20, 2024 at 6:26 PM Mark Wielaard <m...@klomp.org> wrote: > > > > As an experiment Sourceware is now running an forgejo v9 instance at > > https://forge.sourceware.org > > > > Everybody with an @sourceware.org, @cygwin.com or @gcc.gnu.org address > > can register an account (please use the same user name as your account > > name). > > > > The setup has disabled most "extras" (no badges, stars, issues, wikis, > > packages, timetracking, milestones, etc.). And users can only fork > > existing repos (it has mirrors of various sourceware projects). Some > > things haven't been setup yet (external trackers/bugzilla, incoming > > email, ci, etc.) > > > > The full setup can be found in this git repository: > > https://sourceware.org/cgit/forge/ > > > > For now it is only open for existing maintainers/developers for > > experimentating with a pull-request model. We can add others as long > > as they understand this is an experiment and does not mean projects > > are accepting patches through it. Contributions should still be sent > > through the mailinglists. > > Is the pull request to the gcc:gcc-test repo limited? Do you need > extra permissions added to do it? > This was not mentioned so I thought I could register with my > @gcc.gnu.org account as the email and it would work.
Never mind, it is just brokeness of the way of the test repos work. The problem will not show up in the final thing so I am less worried. > > Thanks, > Andrew Pinski > > > > > There is also a new mailinglist for discussion about the setup and the > > best way to create a pull-request workflow. Please subscribe if you > > create an account and mention which project/organization you would > > like do some experiments for. We can then add you to that organization. > > > > https://sourceware.org/mailman/listinfo/forge
