On 31/05/2026 07:27, Andrew Pinski wrote: > On Sat, May 30, 2026 at 10:41 PM Andrew Pinski > <[email protected]> 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. >> ``` > > Not this is directly related to changing MAINTAINERS to be a yaml file. > But I accidently came across: > + - Maintainer: tree browser/unparser > > But the `tree browser` code was removed in r6-2439-g8d2ccbd26694b2 . > So it might be the case that the MAINTAINERS was forgotten to be > updated at the same time. >
Cleaning up the MAINTAINERS entries is certainly something that needs to be done; but my goal at the moment is to be able to show that I can regenerate its contents from the new data structures. So my focus right now is on the data we hold and the tools to do the regeneration. R. > >> >> Thanks, >> Andrea >> >>> >>> jeff
