From: "Sean" <spbrogan@outlook.com>
To: devel@edk2.groups.io, gaoliming@byosoft.com.cn,
'Joey Vagedes' <joey.vagedes@gmail.com>
Cc: 'Abner Chang' <abner.chang@amd.com>,
'Alexei Fedorov' <Alexei.Fedorov@arm.com>,
'Ard Biesheuvel' <ardb+tianocore@kernel.org>,
'Ashraf Ali S' <ashraf.ali.s@intel.com>,
'Chasel Chiu' <chasel.chiu@intel.com>,
'Chen Gang C' <gang.c.chen@intel.com>,
'Daniel Schaefer' <git@danielschaefer.me>,
'Duggapu Chinni B' <chinni.b.duggapu@intel.com>,
'Eric Dong' <eric.dong@intel.com>,
'Gerd Hoffmann' <kraxel@redhat.com>,
'Guo Dong' <guo.dong@intel.com>,
'Guomin Jiang' <guomin.jiang@intel.com>,
'Hao A Wu' <hao.a.wu@intel.com>,
'Igor Kulchytskyy' <igork@ami.com>,
'James Lu' <james.lu@intel.com>,
'Jian J Wang' <jian.j.wang@intel.com>,
'Jiewen Yao' <jiewen.yao@intel.com>,
'Leif Lindholm' <quic_llindhol@quicinc.com>,
'Maciej Rabeda' <maciej.rabeda@linux.intel.com>,
'Michael D Kinney' <michael.d.kinney@intel.com>,
'Michael Kubacki' <mikuback@linux.microsoft.com>,
'Nate DeSimone' <nathaniel.l.desimone@intel.com>,
'Nickle Wang' <nicklew@nvidia.com>,
'Pierre Gondois' <pierre.gondois@arm.com>,
'Rahul Kumar' <rahul1.kumar@intel.com>,
'Ray Han Lim Ng' <ray.han.lim.ng@intel.com>,
'Ray Ni' <ray.ni@intel.com>,
'Sami Mujawar' <sami.mujawar@arm.com>,
'Sean Brogan' <sean.brogan@microsoft.com>,
'Sean Rhodes' <sean@starlabs.systems>,
'Siyuan Fu' <siyuan.fu@intel.com>,
'Star Zeng' <star.zeng@intel.com>,
'Susovan Mohapatra' <susovan.mohapatra@intel.com>,
'Ted Kuo' <ted.kuo@intel.com>, 'Wei6 Xu' <wei6.xu@intel.com>,
'Xiaoyu Lu' <xiaoyu1.lu@intel.com>, 'Yi Li' <yi1.li@intel.com>,
'Zhichao Gao' <zhichao.gao@intel.com>,
'Zhiguang Liu' <zhiguang.liu@intel.com>
Subject: Re: [edk2-devel] 回复: [PATCH v1 00/24] Update Edk2-pytools to latest versions
Date: Thu, 29 Jun 2023 11:01:06 -0700 [thread overview]
Message-ID: <BY3PR19MB49005CF03F038B300F49C6A7C825A@BY3PR19MB4900.namprd19.prod.outlook.com> (raw)
In-Reply-To: <00ec01d9a892$a71e1b40$f55a51c0$@byosoft.com.cn>
Liming,
In general, due to feedback on this list we have tried to require
explicit opt-in for all the stuart based validation tools. So could
that be done yes, but it goes against our current consistent approach of
requiring opt-in and then would put the burden on a platform/package
owner to opt-out if they didn't want this new functionality.
Thanks
Sean
On 6/26/2023 5:59 PM, gaoliming via groups.io wrote:
> Joey:
> So, this change is required for all package YAML. If yes, can PrEval be
> auto set to the package dsc if only one DSC is in Package directory?
next prev parent reply other threads:[~2023-06-29 18:01 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 21:34 [PATCH v1 00/24] Update Edk2-pytools to latest versions Joey Vagedes
2023-06-26 21:34 ` [PATCH v1 01/24] Edk2: edk2-pytools: Update " Joey Vagedes
2023-07-05 17:33 ` Michael Kubacki
2023-06-26 21:34 ` [PATCH v1 02/24] UnitTestFrameworkPkg: CI: Add PrEval entry Joey Vagedes
2023-07-05 17:34 ` [edk2-devel] " Michael Kubacki
2023-06-26 21:34 ` [PATCH v1 03/24] UefiPayloadPkg: " Joey Vagedes
2023-06-26 21:34 ` [PATCH v1 04/24] ArmPkg: " Joey Vagedes
2023-06-26 21:34 ` [PATCH v1 05/24] UefiCpuPkg: " Joey Vagedes
2023-06-26 21:34 ` [PATCH v1 06/24] ArmPlatformPkg: " Joey Vagedes
2023-06-26 21:34 ` [PATCH v1 07/24] CryptoPkg: " Joey Vagedes
2023-08-02 4:41 ` [edk2-devel] " Li, Yi
[not found] ` <1777774354535489.2497@groups.io>
2023-10-07 3:07 ` Li, Yi
2023-10-09 16:26 ` Joey Vagedes via groups.io
2023-06-26 21:34 ` [PATCH v1 08/24] DynamicTablesPkg: " Joey Vagedes
2023-07-06 15:36 ` Sami Mujawar
2023-06-26 21:34 ` [PATCH v1 09/24] EmbeddedPkg: " Joey Vagedes
2023-06-28 6:20 ` Chang, Abner
2023-06-26 21:34 ` [PATCH v1 10/24] FatPkg: " Joey Vagedes
2023-06-26 21:34 ` [PATCH v1 11/24] FmpDevicePkg: " Joey Vagedes
2023-06-26 21:34 ` [PATCH v1 12/24] IntelFsp2Pkg: " Joey Vagedes
2023-08-07 22:57 ` [edk2-devel] " Nate DeSimone
2023-06-26 21:34 ` [PATCH v1 13/24] CryptoPkg: " Joey Vagedes
2023-10-09 16:49 ` [edk2-devel] [PATCH v1 13/24] StandaloneMmPkg: " Joey Vagedes via groups.io
2023-10-10 7:44 ` Ard Biesheuvel
2023-06-26 21:34 ` [PATCH v1 14/24] SourceLevelDebugPkg: " Joey Vagedes
2023-06-26 21:34 ` [PATCH v1 15/24] SignedCapsulePkg: " Joey Vagedes
2023-06-26 21:34 ` [PATCH v1 16/24] ShellPkg: " Joey Vagedes
2023-06-26 21:34 ` [PATCH v1 17/24] SecurityPkg: " Joey Vagedes
2023-06-26 21:34 ` [PATCH v1 18/24] RedfishPkg: " Joey Vagedes
2023-06-28 6:20 ` Chang, Abner
2023-06-26 21:34 ` [PATCH v1 19/24] PrmPkg: " Joey Vagedes
2023-07-05 17:34 ` [edk2-devel] " Michael Kubacki
2023-08-07 22:57 ` Nate DeSimone
2023-06-26 21:34 ` [PATCH v1 20/24] PcAtChipsetPkg: " Joey Vagedes
2023-06-26 21:34 ` [PATCH v1 21/24] NetworkPkg: " Joey Vagedes
2023-06-26 21:34 ` [PATCH v1 22/24] MdePkg: " Joey Vagedes
2023-06-26 21:34 ` [PATCH v1 23/24] MdeModulePkg: " Joey Vagedes
2023-06-26 21:34 ` [PATCH v1 24/24] IntelFsp2WrapperPkg: " Joey Vagedes
2023-08-07 22:57 ` [edk2-devel] " Nate DeSimone
2023-06-27 0:59 ` 回复: [PATCH v1 00/24] Update Edk2-pytools to latest versions gaoliming
2023-06-27 16:58 ` Joey Vagedes
2023-06-29 18:01 ` Sean [this message]
2023-06-30 1:50 ` 回复: [edk2-devel] 回复: " gaoliming
2023-07-06 15:22 ` Joey Vagedes
2023-08-01 16:16 ` [edk2-devel] " Joey Vagedes via groups.io
2023-08-02 3:14 ` [edk2-devel] 回复: " gaoliming via groups.io
2023-08-23 17:14 ` [edk2-devel] " Joey Vagedes via groups.io
2023-10-02 22:20 ` Joey Vagedes via groups.io
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=BY3PR19MB49005CF03F038B300F49C6A7C825A@BY3PR19MB4900.namprd19.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