From: "Laszlo Ersek" <lersek@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
devel@edk2.groups.io, liming.gao@intel.com,
"Leif Lindholm" <leif.lindholm@linaro.org>
Cc: Andrew Fish <afish@apple.com>,
Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [Patch] Maintainers.txt: Move ShellBin maintainers to EDK II Releases section
Date: Tue, 24 Sep 2019 19:17:20 +0200 [thread overview]
Message-ID: <dd086c77-ba6f-339f-bc29-f06faa9c8be0@redhat.com> (raw)
In-Reply-To: <057d571d-2a84-a08d-377f-f2f443219e81@redhat.com>
On 09/24/19 12:41, Philippe Mathieu-Daudé wrote:
> Hi Liming,
>
> On 9/24/19 3:19 AM, Liming Gao wrote:
>> ShellBinPkg is generated for each edk2 stable tag release.
>>
>> Cc: Andrew Fish <afish@apple.com>
>> Cc: Laszlo Ersek <lersek@redhat.com>
>> Cc: Leif Lindholm <leif.lindholm@linaro.org>
>> Cc: Michael D Kinney <michael.d.kinney@intel.com>
>> Signed-off-by: Liming Gao <liming.gao@intel.com>
>> ---
>> Maintainers.txt | 13 ++++++-------
>> 1 file changed, 6 insertions(+), 7 deletions(-)
>>
>> diff --git a/Maintainers.txt b/Maintainers.txt
>> index f348d70df3..f75b35d5a8 100644
>> --- a/Maintainers.txt
>> +++ b/Maintainers.txt
>> @@ -82,6 +82,12 @@ EDK II Releases:
>> W: https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning
>> M: Liming Gao <liming.gao@intel.com>
>>
>
> Shouldn't you keep the F: tag too? Maybe:
>
> ShellPkg
> (stable)
> F: ShellPkg/
I think we should keep "F:" only if the related "M:" entries work as
expected, with the "BaseTools/Scripts/GetMaintainer.py" script.
(I haven't checked.)
Thanks
Laszlo
>
>
>> +W: https://github.com/tianocore/edk2/releases/download/edk2-stable20XXXX/ShellBinPkg.zip
>> +M: Ray Ni <ray.ni@intel.com> (Ia32/X64)
>> +M: Zhichao Gao <zhichao.gao@intel.com> (Ia32/X64)
>> +M: Leif Lindholm <leif.lindholm@linaro.org> (ARM/AArch64)
>> +M: Ard Biesheuvel <ard.biesheuvel@linaro.org> (ARM/AArch64)
>> +
>> EDK II Architectures:
>> ---------------------
>> ARM, AARCH64
>> @@ -421,13 +427,6 @@ W: https://github.com/tianocore/tianocore.github.io/wiki/ShellPkg
>> M: Ray Ni <ray.ni@intel.com>
>> M: Zhichao Gao <zhichao.gao@intel.com>
>>
>> -Maintainers for stable Shell binaries generation
>> -when need to publish Shell binaries with edk2 release:
>> -M: Ray Ni <ray.ni@intel.com> (Ia32/X64)
>> -M: Zhichao Gao <zhichao.gao@intel.com> (Ia32/X64)
>> -M: Leif Lindholm <leif.lindholm@linaro.org> (ARM/AArch64)
>> -M: Ard Biesheuvel <ard.biesheuvel@linaro.org> (ARM/AArch64)
>> -
>> SignedCapsulePkg
>> F: SignedCapsulePkg/
>> W: https://github.com/tianocore/tianocore.github.io/wiki/SignedCapsulePkg
>>
next prev parent reply other threads:[~2019-09-24 17:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 1:19 [Patch] Maintainers.txt: Move ShellBin maintainers to EDK II Releases section Liming Gao
2019-09-24 10:41 ` [edk2-devel] " Philippe Mathieu-Daudé
2019-09-24 15:08 ` Liming Gao
2019-09-24 15:12 ` Philippe Mathieu-Daudé
2019-09-24 15:17 ` Liming Gao
2019-09-24 15:25 ` Philippe Mathieu-Daudé
2019-09-24 17:17 ` Laszlo Ersek [this message]
2019-09-24 17:26 ` Laszlo Ersek
2019-09-25 0:43 ` Liming Gao
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=dd086c77-ba6f-339f-bc29-f06faa9c8be0@redhat.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