From: "Chiu, Chasel" <chasel.chiu@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Guo, Gua" <gua.guo@intel.com>,
"Gao, Liming" <gaoliming@byosoft.com.cn>
Cc: Andrew Fish <afish@apple.com>,
Leif Lindholm <quic_llindhol@quicinc.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [PATCH v1 0/1] Maintainers.txt: Update reviewers and maintainer for FdtLib
Date: Fri, 12 May 2023 02:35:21 +0000 [thread overview]
Message-ID: <BN9PR11MB5483ED76596D8405B4A881A6E6759@BN9PR11MB5483.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BL1PR11MB5478FD5E10941483796CDCE5EF759@BL1PR11MB5478.namprd11.prod.outlook.com>
Hi Liming,
We are considering this is a missing when merging FdtLib support earlier.
Do we need to wait for Stewards approval for adding maintainers?
Thanks,
Chasel
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Guo, Gua
> Sent: Thursday, May 11, 2023 7:31 PM
> To: devel@edk2.groups.io; Gao, Liming <gaoliming@byosoft.com.cn>
> Subject: Re: [edk2-devel] [PATCH v1 0/1] Maintainers.txt: Update reviewers and
> maintainer for FdtLib
>
> Hi Liming,
>
> Do you know whether for code freeze also include Maintainers.txt update ?
> Or maybe we can submit it once the change approve.
>
> Thanks,
> Gua
> -----Original Message-----
> From: Guo, Gua <gua.guo@intel.com>
> Sent: Friday, May 12, 2023 10:11 AM
> To: devel@edk2.groups.io
> Cc: Guo, Gua <gua.guo@intel.com>
> Subject: [PATCH v1 0/1] Maintainers.txt: Update reviewers and maintainer for
> FdtLib
>
> From: Gua Guo <gua.guo@intel.com>
>
> V1
> PR: https://github.com/tianocore/edk2/pull/4389
> Maintainer: Benny Lin <benny.lin@intel.com>
> Reviewer: Gua Guo <gua.guo@intel.com>
> Reviewer: Chasel Chiu <chasel.chiu@intel.com>
> Reviewer: James Lu <james.lu@intel.com>
>
> Gua Guo (1):
> Maintainers.txt: Update reviewers and maintainers for FdtLib. Update
> reviewers and maintainers for FdtLib.
>
> Maintainers.txt | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> --
> 2.39.2.windows.1
>
>
>
>
>
next prev parent reply other threads:[~2023-05-12 2:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 2:10 [PATCH v1 0/1] Maintainers.txt: Update reviewers and maintainer for FdtLib Guo, Gua
2023-05-12 2:10 ` [PATCH v1 1/1] Maintainers.txt: Update reviewers and maintainers for FdtLib. Update reviewers and maintainers " Guo, Gua
2023-05-12 2:17 ` Benny Lin
2023-05-12 2:40 ` Chiu, Chasel
2023-05-12 2:20 ` [edk2-devel] [PATCH v1 0/1] Maintainers.txt: Update reviewers and maintainer " Chiu, Chasel
2023-05-12 2:30 ` Guo, Gua
2023-05-12 2:35 ` Chiu, Chasel [this message]
2023-05-12 2:44 ` 回复: [edk2-devel] " gaoliming
2023-05-12 7:10 ` Chiu, Chasel
[not found] ` <175E53D0D22F3B03.30531@groups.io>
2023-05-12 7:15 ` Chiu, Chasel
2023-05-15 1:01 ` 回复: " gaoliming
2023-05-15 19:23 ` Chiu, Chasel
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-list 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=BN9PR11MB5483ED76596D8405B4A881A6E6759@BN9PR11MB5483.namprd11.prod.outlook.com \
--to=devel@edk2.groups.io \
/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