-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Closed
Labels
A-docsArea: Documentation for any part of the project, including the compiler, standard library, and toolsArea: Documentation for any part of the project, including the compiler, standard library, and toolsA-targetsArea: Concerning the implications of different compiler targetsArea: Concerning the implications of different compiler targetsC-bugCategory: This is a bug.Category: This is a bug.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Description
We have a bunch of Arm targets maintained by "Rust Embedded Devices Working Group Cortex-M Team", for example thumbv8m.base-none-eabi.
The link there is not very useful as it doesn't tell us who these people are (to ping them for problems), and if I poke around the org I find the wg
repo which contains names, but only lists an "Arm team": https://github.com/rust-embedded/wg?tab=readme-ov-file#the-arm-team
Is this team responsible for these targets and should we ping all these people for issues? We'd appreciate a clarification PR that either links to a list of people, or lists the people directly.
@adamgreig @berkus @jonathanpallant @nchong-at-aws @newAM @raw-bin @thalesfragoso @therealprof as the people on the Arm team
Metadata
Metadata
Assignees
Labels
A-docsArea: Documentation for any part of the project, including the compiler, standard library, and toolsArea: Documentation for any part of the project, including the compiler, standard library, and toolsA-targetsArea: Concerning the implications of different compiler targetsArea: Concerning the implications of different compiler targetsC-bugCategory: This is a bug.Category: This is a bug.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.