From: "Liu, Hongtao" <hongtao.liu@intel.com>
To: "Cui, Lili" <lili.cui@intel.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: RE: [PATCH] MAINTAINERS: Add myself for write after approval
Date: Wed, 12 Oct 2022 07:54:46 +0000 [thread overview]
Message-ID: <CY4PR1101MB2150D7A9B06E4D07741E506CE5229@CY4PR1101MB2150.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221012075014.2922-1-lili.cui@intel.com>
> -----Original Message-----
> From: Cui, Lili <lili.cui@intel.com>
> Sent: Wednesday, October 12, 2022 3:50 PM
> To: gcc-patches@gcc.gnu.org
> Cc: Liu, Hongtao <hongtao.liu@intel.com>
> Subject: [PATCH] MAINTAINERS: Add myself for write after approval
>
> Hi,
>
> I want to add myself in MAINTANINER for write after approval.
>
> OK for master?
Obvious fixes can be committed without prior approval(https://gcc.gnu.org/gitwrite.html).
This can be considered as an obvious fix(But you still need to send the patch out like this).
>
> ChangeLog:
> * MAINTAINERS (Write After Approval): Add myself.
>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 11fa8bc6dbd..e4e7349a6d9 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -377,6 +377,7 @@ Andrea Corallo
> <andrea.corallo@arm.com>
> Christian Cornelssen <ccorn@cs.tu-berlin.de>
> Ludovic Courtès <ludo@gnu.org>
> Lawrence Crowl <crowl@google.com>
> +Lili Cui <lili.cui@intel.com>
> Ian Dall <ian@beware.dropbear.id.au>
> David Daney
> <david.daney@caviumnetworks.com>
> Robin Dapp <rdapp@linux.ibm.com>
> --
> 2.17.1
next prev parent reply other threads:[~2022-10-12 7:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 7:50 Cui,Lili
2022-10-12 7:54 ` Liu, Hongtao [this message]
[not found] <20220627075659.17086-1-lingling.kong@intel.com>
2022-06-27 8:04 ` Kong, Lingling
2022-06-27 8:29 ` Hongyu Wang
2022-06-27 8:32 ` Hongyu Wang
2022-06-28 1:38 ` Kong, Lingling
-- strict thread matches above, loose matches on Subject: below --
2021-10-19 11:23 CHIGOT, CLEMENT
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=CY4PR1101MB2150D7A9B06E4D07741E506CE5229@CY4PR1101MB2150.namprd11.prod.outlook.com \
--to=hongtao.liu@intel.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=lili.cui@intel.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).