public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Christoph Muellner <christoph.muellner@vrull.eu>
To: gcc-patches@gcc.gnu.org, Kito Cheng <kito.cheng@sifive.com>,
	Philipp Tomsich <philipp.tomsich@vrull.eu>,
	Jeff Law <jeffreyalaw@gmail.com>
Cc: "Christoph Müllner" <christoph.muellner@vrull.eu>
Subject: [COMMITTED] MAINTAINERS: Add myself to write after approval
Date: Tue, 10 Oct 2023 14:40:32 +0200	[thread overview]
Message-ID: <20231010124032.103935-1-christoph.muellner@vrull.eu> (raw)

From: Christoph Müllner <christoph.muellner@vrull.eu>

Signed-off-by: Christoph Müllner <christoph.muellner@vrull.eu>

ChangeLog:

	* MAINTAINERS: Add myself.
---
 MAINTAINERS | 1 +
 1 file changed, 1 insertion(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index e9154878517..aa441de5332 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -576,6 +576,7 @@ Catherine Moore					<clm@codesourcery.com>
 James A. Morrison				<phython@gcc.gnu.org>
 Brooks Moses					<bmoses@google.com>
 Dirk Mueller					<dmueller@suse.de>
+Christoph Müllner				<christoph.muellner@vrull.eu>
 Phil Muldoon					<pmuldoon@redhat.com>
 Gaius Mulley					<gaiusmod2@gmail.com>
 Steven Munroe					<munroesj52@gmail.com>
-- 
2.41.0


             reply	other threads:[~2023-10-10 12:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10 12:40 Christoph Muellner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-09 21:14 Jivan Hakobyan
2023-08-29 11:23 Tsukasa OI
2023-08-11 17:30 Eric Feng
2023-08-01 13:56 [committed] " Richard Ball
2023-07-31  1:25 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=20231010124032.103935-1-christoph.muellner@vrull.eu \
    --to=christoph.muellner@vrull.eu \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=kito.cheng@sifive.com \
    --cc=philipp.tomsich@vrull.eu \
    /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).