From: "Kong, Lingling" <lingling.kong@intel.com>
To: Hongyu Wang <wwwhhhyyy333@gmail.com>
Cc: "Liu, Hongtao" <hongtao.liu@intel.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"Kong, Lingling" <lingling.kong@intel.com>
Subject: RE: [PATCH] MAINTAINERS: Add myself for write after approval
Date: Tue, 28 Jun 2022 01:38:59 +0000 [thread overview]
Message-ID: <DM4PR11MB5487FAAFD335355033055608ECB89@DM4PR11MB5487.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CA+OydWk3Qe3Rj_DfQf6kifNTSG6CEM_ASKVdUdsHsHDyz2C_FQ@mail.gmail.com>
Thanks a lot! I fixed it.
ChangeLog:
* MAINTAINERS (Write After Approval): Add myself.
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 54d8ad41a6f..151770f59f4 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -478,6 +478,7 @@ Jeff Knaggs <jknaggs@redhat.com>
Michael Koch <konqueror@gmx.de>
Nicolas Koenig <koenigni@student.ethz.ch>
Boris Kolpackov <boris@codesynthesis.com>
+Lingling Kong <lingling.kong@intel.com>
Dave Korn <dave.korn.cygwin@gmail.com>
Julia Koval <julia.koval@intel.com>
Matt Kraai <kraai@ftbfs.org>
--
2.18.2
> -----Original Message-----
> From: Hongyu Wang <wwwhhhyyy333@gmail.com>
> Sent: Monday, June 27, 2022 4:32 PM
> To: Kong, Lingling <lingling.kong@intel.com>
> Cc: Liu, Hongtao <hongtao.liu@intel.com>; gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] MAINTAINERS: Add myself for write after approval
>
> Sorry, should be between
>
> Boris Kolpackov <boris@codesynthesis.com> Dave Korn
> <dave.korn.cygwin@gmail.com>
>
> Hongyu Wang <wwwhhhyyy333@gmail.com> 于2022年6月27日周一 16:29
> 写道:
> >
> > According to the official guide, please sort your last name in
> > alphabetical order, which means you shold put your name between
> >
> > Dave Korn <dave.korn.cygwin@gmail.com> Julia Koval
> > <julia.koval@intel.com>
> >
> > Kong, Lingling via Gcc-patches <gcc-patches@gcc.gnu.org> 于2022年6月27
> 日周一
> > 16:05写道:
> >
> > >
> > > Hi,
> > >
> > > I want to add myself in MAINTANINER for write after approval.
> > >
> > > OK for master?
> > >
> > > ChangeLog:
> > >
> > > * MAINTAINERS (Write After Approval): Add myself.
> > > ---
> > > MAINTAINERS | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
> > > diff --git a/MAINTAINERS b/MAINTAINERS index
> > > 54d8ad41a6f..49627e5d113 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -698,6 +698,7 @@ Shujing Zhao
> <pearly.zhao@oracle.com>
> > > Jon Ziegler <jonz@apple.com>
> > > Roman Zippel <zippel@linux-m68k.org>
> > > Josef Zlomek <josef.zlomek@email.cz>
> > > +Lingling Kong <lingling.kong@intel.com>
> > >
> > > Bug database only accounts
> > >
> > > --
> > > 2.18.1
> > >
next prev parent reply other threads:[~2022-06-28 1:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2022-10-12 7:50 Cui,Lili
2022-10-12 7:54 ` Liu, Hongtao
-- 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=DM4PR11MB5487FAAFD335355033055608ECB89@DM4PR11MB5487.namprd11.prod.outlook.com \
--to=lingling.kong@intel.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hongtao.liu@intel.com \
--cc=wwwhhhyyy333@gmail.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).