public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Edelsohn <dje.gcc@gmail.com>
To: YunQiang Su <yunqiang.su@cipunited.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: YunQiang Su appointed MIPS maintainer
Date: Thu, 1 Jun 2023 13:08:30 -0400	[thread overview]
Message-ID: <CAGWvnymWQzD4Ng-aUnUZ78kFbetMSiOj4qQzgG5bmOv0y02OmA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 678 bytes --]

I am pleased to announce that the GCC Steering Committee has appointed
YunQiang Su as MIPS maintainer.

Please note that this is somewhat provisional because MIPS needs a
full-time maintainer, but you do not have a long history of experience in
the GCC Community.  Please continue to be vigilant about GCC Coding
Standards.  You might consider initially continuing to post your MIPS
patches a few days before you commit them in your role as maintainer to
allow other developers the opportunity to provide feedback, if they so wish.

Please join me in congratulating YunQiang on his new role.

YunQiang, please update your listings in the MAINTAINERS file.

Happy hacking!
David

                 reply	other threads:[~2023-06-01 17:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGWvnymWQzD4Ng-aUnUZ78kFbetMSiOj4qQzgG5bmOv0y02OmA@mail.gmail.com \
    --to=dje.gcc@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=yunqiang.su@cipunited.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).