Hi gcc-patches mailing list, Richard Earnshaw via Sourceware Forge <[email protected]> has requested that the following forgejo pull request be published on the mailing list.
Created on: 2026-06-05 16:16:49+00:00 Latest update: 2026-06-05 16:17:09+00:00 Changes: 1 changed files, 13 additions, 0 deletions Head revision: rearnsha/gcc-TEST ref codeowners-expt commit cb1382b99dd2fcdcc17a5d09bf03d780373f248d Base revision: gcc/gcc-TEST ref trunk commit 666e349a989ae51e05463317019efa6b20c7c3b1 r17-1376-g666e349a989ae5 Merge base: 666e349a989ae51e05463317019efa6b20c7c3b1 Full diff url: https://forge.sourceware.org/gcc/gcc-TEST/pulls/171.diff Discussion: https://forge.sourceware.org/gcc/gcc-TEST/pulls/171 Requested Reviewers: rdfm Many forge instances support a CODEOWNERS file as a way of automatically requesting reviewers. Forgejo is no different, though the syntax is not the same as some other forge instances; so put this in the .forgejo directory. This version is for experimenting with the format. I expect to want this file to be autogenerated from other data at a later stage. ChangeLog: * .forgejo/CODEOWNERS: New file. Thanks for taking the time to contribute to GCC! Please be advised that https://forge.sourceware.org/ is currently a trial that is being used by the GCC community to experiment with a new workflow based on pull requests. Pull requests sent here may be forgotten or ignored. Patches that you want to propose for inclusion in GCC should use the existing email-based workflow, see https://gcc.gnu.org/contribute.html Changed files: - A: .forgejo/CODEOWNERS Richard Earnshaw (1): forge: Add a prototype CODEOWNERS file .forgejo/CODEOWNERS | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 .forgejo/CODEOWNERS -- 2.54.0
