public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Ball <richard.ball@arm.com>
To: gcc-patches@gcc.gnu.org, richard.sandiford@arm.com
Subject: [committed] MAINTAINERS: Add myself to write after approval
Date: Tue, 1 Aug 2023 14:56:16 +0100	[thread overview]
Message-ID: <6fbb9f2b-1496-f2be-c9e9-965d560beae5@arm.com> (raw)

Sponsored by Richard Sandiford <Richard.Sandiford@arm.com>

ChangeLog:

	* MAINTAINERS: Add myself.

###########################################################

diff --git a/MAINTAINERS b/MAINTAINERS
index 49aa6bae73b..a8bb43f50c3 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -332,6 +332,7 @@ David Ayers 
<ayers@fsfe.org>
  Prakhar Bahuguna                               <prakhar.bahuguna@arm.com>
  Giovanni Bajo                                  <giovannibajo@gcc.gnu.org>
  Simon Baldwin                                  <simonb@google.com>
+Richard Ball                                   <richard.ball@arm.com>
  Scott Bambrough 
<scottb@netwinder.org>
  Wolfgang Bangerth                              <bangerth@dealii.org>
  Gergö Barany                                   <gergo@codesourcery.com>

             reply	other threads:[~2023-08-01 13:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 13:56 Richard Ball [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-09 21:14 [COMMITTED] " Jivan Hakobyan
2023-10-10 12:40 Christoph Muellner
2023-08-29 11:23 Tsukasa OI
2023-08-11 17:30 Eric Feng
2023-07-31  1:25 [committed] " Li Xu
2023-07-21 18:11 [COMMITTED] " Cupertino Miranda
2023-06-25  9:51 [committed] " Lehua Ding
2023-05-10 16:10 pan2.li
2023-04-26 16:08 [PATCH] " Palmer Dabbelt
2023-04-26 16:15 ` [committed] " Patrick O'Neill
2022-09-23 10:39 [committed] MAINTAINERS: Add myself to Write After Approval Paul-Antoine Arras
2022-07-15 13:50 Andrew Carlotti

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=6fbb9f2b-1496-f2be-c9e9-965d560beae5@arm.com \
    --to=richard.ball@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.sandiford@arm.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).