From: Paul-Antoine Arras <pa@codesourcery.com>
To: <gcc-patches@gcc.gnu.org>
Subject: [committed] MAINTAINERS: Add myself to Write After Approval
Date: Fri, 23 Sep 2022 12:39:43 +0200 [thread overview]
Message-ID: <a8bae7c0-2c0a-7022-9b7b-8ca41ef01544@codesourcery.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 91 bytes --]
Hello,
I just added myself to the Write After Approval section of MAINTAINERS file.
--
PA
[-- Attachment #2: 0001-MAINTAINERS-Add-myself-to-Write-After-Approval.patch --]
[-- Type: text/plain, Size: 757 bytes --]
From d10308ff618e036d6c3d1a8c491ca4755b257612 Mon Sep 17 00:00:00 2001
From: Paul-Antoine Arras <pa@codesourcery.com>
Date: Fri, 23 Sep 2022 10:21:48 +0000
Subject: [PATCH] MAINTAINERS: Add myself to Write After Approval
ChangeLog:
* MAINTAINERS (Write After Approval): Add myself.
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git MAINTAINERS MAINTAINERS
index be146855ed8..f63de226609 100644
--- MAINTAINERS
+++ MAINTAINERS
@@ -316,6 +316,7 @@ from other maintainers or reviewers.
Mark G. Adams <mark.g.adams@sympatico.ca>
Pedro Alves <palves@redhat.com>
+Paul-Antoine Arras <pa@codesourcery.com>
Raksit Ashok <raksit@google.com>
Matt Austern <austern@google.com>
David Ayers <ayers@fsfe.org>
--
2.31.1
next reply other threads:[~2022-09-23 10:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 10:39 Paul-Antoine Arras [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-09 21:14 [COMMITTED] MAINTAINERS: Add myself to write after approval Jivan Hakobyan
2023-10-10 12:40 Christoph Muellner
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-07-15 13:50 [committed] MAINTAINERS: Add myself to Write After Approval 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=a8bae7c0-2c0a-7022-9b7b-8ca41ef01544@codesourcery.com \
--to=pa@codesourcery.com \
--cc=gcc-patches@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).