public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: YunQiang Su <syq@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-1879] MAINTAINERS: move Matthew Fortune to Write After Approval
Date: Fri, 16 Jun 2023 08:09:49 +0000 (GMT) [thread overview]
Message-ID: <20230616080949.5F2AC3858431@sourceware.org> (raw)
https://gcc.gnu.org/g:0f732ff7c4724e3317ce64feb757d5112c6e1f94
commit r14-1879-g0f732ff7c4724e3317ce64feb757d5112c6e1f94
Author: YunQiang Su <yunqiang.su@cipunited.com>
Date: Mon Jun 5 09:36:01 2023 +0800
MAINTAINERS: move Matthew Fortune to Write After Approval
In 4fe6e12204535545edf7f035d4dc79c1404058cf, I should have added
Matthew Fortune to the Write After Approval section, while replacing
the MIPS Maintainer position.
ChangeLog:
* MAINTAINERS (Write After Approval): move Matthew Fortune
to Write After Approval.
Diff:
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 4a9a656647e..4825ee449ae 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -412,6 +412,7 @@ Li Feng <nemokingdom@gmail.com>
Thomas Fitzsimmons <fitzsim@redhat.com>
Alexander Fomin <afomin.mailbox@gmail.com>
Brian Ford <ford@vss.fsi.com>
+Matthew Fortune <mfortune@gmail.com>
John Freeman <jfreeman08@gmail.com>
Nathan Froyd <froydnj@gcc.gnu.org>
Chao-ying Fu <fu@mips.com>
reply other threads:[~2023-06-16 8:09 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=20230616080949.5F2AC3858431@sourceware.org \
--to=syq@gcc.gnu.org \
--cc=gcc-cvs@gcc.gnu.org \
/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).