On 31/05/2026 06:41, Andrew Pinski wrote: > On Fri, May 29, 2026 at 10:37 AM Jeffrey Law > <[email protected]> wrote: >> >> >> >> On 5/29/2026 9:16 AM, Richard Earnshaw via Sourceware Forge wrote: >>> From: Richard Earnshaw <[email protected]> >>> >>> Convert the existing MAINTAINERS data to YAML and add a script to >>> rebuild the MAINTAINERS file from it. >>> >>> ChangeLog: >>> >>> * MAINTAINERS: Regenerate from MAINTAINERS.yml >>> >>> contrib/ChangeLog: >>> >>> * MAINTAINERS.yml: New file. >>> * gen-MAINTAINERS.py: New file. >> Works for me. If there aren't objections by say Tues next week, go for it. > > Make sure https://gcc.gnu.org/gitwrite.html#authenticated gets updated > for the new way of adding yourself for write after approval. Right now > it reads: > ``` > At this point, check out a tree using the instructions below and add > yourself to the MAINTAINERS file. Note: Your first and last names must > be exactly the same between your account on gcc.gnu.org and the > MAINTAINERS file. Place your name in the correct section following the > conventions specified in the file (e.g. "Write After Approval" is > "last name alphabetical order"). If you do not have an FSF copyright > assignment on file, also add yourself to the DCO section in the file. > ``` >
Thanks for the pointer. This isn't a finished patch yet - hence the WIP/RFD tags on the cover letter. There are a number of other changes needed yet as well, such as changing the MAINTAINERS test in the testsuite to check that it correctly regenerates the current MAINTAINERS file. > Thanks, > Andrea > >> >> jeff
