From: juzhe.zhong@rivai.ai
To: gcc-patches@gcc.gnu.org
Cc: kito.cheng@gmail.com, palmer@dabbelt.com, jeffreyalaw@gmail.com,
Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
Subject: [PATCH] Add myself to write after approval
Date: Wed, 26 Apr 2023 10:01:59 +0800 [thread overview]
Message-ID: <20230426020159.2497257-1-juzhe.zhong@rivai.ai> (raw)
From: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
ChangeLog:
* MAINTAINERS: Add myself.
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 4fbfa01c111..b91f49dec96 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -715,6 +715,7 @@ Shujing Zhao <pearly.zhao@oracle.com>
Jon Ziegler <jonz@apple.com>
Roman Zippel <zippel@linux-m68k.org>
Josef Zlomek <josef.zlomek@email.cz>
+Juzhe Zhong <juzhe.zhong@rivai.ai>
Bug database only accounts
--
2.36.3
next reply other threads:[~2023-04-26 2:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 2:01 juzhe.zhong [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-11 14:21 Paul Iannetta
2002-05-24 0:53 [PATCH] add myself to Write After Approval kaz Kojima
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=20230426020159.2497257-1-juzhe.zhong@rivai.ai \
--to=juzhe.zhong@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.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).