public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@embecosm.com>
To: YunQiang Su <yunqiang.su@cipunited.com>
Cc: Matthew Fortune <mfortune@gmail.com>,
	gcc-patches@gcc.gnu.org,  richard.sandiford@arm.com,
	Jeff Law <jeffreyalaw@gmail.com>,
	 David Edelsohn <dje.gcc@gmail.com>,
	 "Maciej W. Rozycki" <macro@orcam.me.uk>
Subject: Re: [COMMITTED] MAINTAINERS: Add myself as MIPS port maintainer
Date: Sat, 3 Jun 2023 15:51:36 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.2.20.2306031545510.28892@tpp.orcam.me.uk> (raw)
In-Reply-To: <20230602021059.2229464-1-yunqiang.su@cipunited.com>

On Fri, 2 Jun 2023, YunQiang Su wrote:

> diff --git a/MAINTAINERS b/MAINTAINERS
> index 4a7c963914b..c8b787b6e1e 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -91,7 +91,7 @@ m68k port		Andreas Schwab		<schwab@linux-m68k.org>
>  m68k-motorola-sysv port	Philippe De Muyter	<phdm@macqel.be>
>  mcore port		Nick Clifton		<nickc@redhat.com>
>  microblaze		Michael Eager		<eager@eagercon.com>
> -mips port		Matthew Fortune		<mfortune@gmail.com>
> +mips port		YunQiang Su		<yunqiang.su@cipunited.com>

 Has Matthew agreed to be removed from the maintainer's post?  Even if so,
then he needs to be moved back to the Write After Approval section, as no
one has deprived him of this right.

  Maciej

  reply	other threads:[~2023-06-03 14:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02  2:10 YunQiang Su
2023-06-03 14:51 ` Maciej W. Rozycki [this message]
2023-06-04 17:33   ` Matthew Fortune
2023-06-05  1:50     ` [PATCH] MAINTAINERS: move Matthew Fortune to Write After Approval YunQiang Su

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=alpine.DEB.2.20.2306031545510.28892@tpp.orcam.me.uk \
    --to=macro@embecosm.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=macro@orcam.me.uk \
    --cc=mfortune@gmail.com \
    --cc=richard.sandiford@arm.com \
    --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).