From: Jivan Hakobyan <jivanhakobyan9@gmail.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Jeff Law <jlaw@ventanamicro.com>
Subject: [COMMITTED] MAINTAINERS: Add myself to write after approval
Date: Fri, 10 Nov 2023 01:14:33 +0400 [thread overview]
Message-ID: <CAHso6sOovz+wFZ43H6jTqX+Mq1j_=z9RxBfFTqj4Awxy7gSzZw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
MAINTAINERS: Add myself to write after approval
Signed-off-by: Jeff Law <jeffreyalaw@gmail.com>
ChangeLog:
* MAINTAINERS: Add myself.
diff --git a/MAINTAINERS b/MAINTAINERS
index 30cb530a3b1..c43167d9a75 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -445,6 +445,7 @@ Wei Guozhi <
carrot@google.com>
Vineet Gupta <vineetg@rivosinc.com>
Naveen H.S <naveenh@marvell.com>
Mostafa Hagog <hagog@gcc.gnu.org>
+Jivan Hakobyan <jivanhakobyan9@gmail.com>
Andrew Haley <aph@redhat.com>
Frederik Harwath <frederik@codesourcery.com>
Stuart Hastings <stuart@apple.com>
--
With the best regards
Jivan Hakobyan
next reply other threads:[~2023-11-09 21:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 21:14 Jivan Hakobyan [this message]
-- strict thread matches above, loose matches on Subject: below --
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-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='CAHso6sOovz+wFZ43H6jTqX+Mq1j_=z9RxBfFTqj4Awxy7gSzZw@mail.gmail.com' \
--to=jivanhakobyan9@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jlaw@ventanamicro.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).