From: "Leif Lindholm" <leif.lindholm@linaro.org>
To: devel@edk2.groups.io, liming.gao@intel.com
Cc: Ray Ni <ray.ni@intel.com>, Andrew Fish <afish@apple.com>,
Laszlo Ersek <lersek@redhat.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Jian J Wang <jian.j.wang@intel.com>,
Hao A Wu <hao.a.wu@intel.com>, Bob Feng <bob.c.feng@intel.com>,
Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [Patch 0/5] Rename tool chain name CLANG9 to CLANGPDB
Date: Thu, 14 Nov 2019 14:44:41 +0000 [thread overview]
Message-ID: <20191114144441.GH7323@bivouac.eciton.net> (raw)
In-Reply-To: <1573719880-6820-1-git-send-email-liming.gao@intel.com>
On Thu, Nov 14, 2019 at 04:24:35PM +0800, Liming Gao wrote:
> BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=2341
>
> Based on feedback from https://edk2.groups.io/g/devel/message/50466,
> CLANGPDB is the most acceptable tool chain name. Wiki will be updated.
>
> This patch set only changes the tool chain name. There is no
> code logic change. OvmfIa32X64 and Emulator are verified.
>
> This patch set is to catch 201911 stable tag.
I'm fine with that, and the name.
> Cc: Ray Ni <ray.ni@intel.com>
> Cc: Andrew Fish <afish@apple.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Cc: Jordan Justen <jordan.l.justen@intel.com>
> Cc: Jian J Wang <jian.j.wang@intel.com>
> Cc: Hao A Wu <hao.a.wu@intel.com>
> Cc: Bob Feng <bob.c.feng@intel.com>
> Cc: Leif Lindholm <leif.lindholm@linaro.org>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Liming Gao (5):
> BaseTools: Rename tool chain CLANG9 to CLANGPDB
> MdeModulePkg RegularExpressionDxe: Update tool chain name to CLANGPDB
> CryptoPkg CryptoLib: Update tool chain name to CLANGPDB
> OvmfPkg DSC: Update tool chain name to CLANGPDB
> EmulatorPkg DSC and WinHost.inf: Update tool chain name to CLANGPDB
>
> BaseTools/Conf/build_rule.template | 14 +-
> BaseTools/Conf/tools_def.template | 156 ++++++++++-----------
> CryptoPkg/Library/BaseCryptLib/BaseCryptLib.inf | 2 +-
> CryptoPkg/Library/BaseCryptLib/PeiCryptLib.inf | 2 +-
> CryptoPkg/Library/BaseCryptLib/RuntimeCryptLib.inf | 2 +-
> CryptoPkg/Library/BaseCryptLib/SmmCryptLib.inf | 2 +-
> CryptoPkg/Library/OpensslLib/OpensslLib.inf | 2 +-
> CryptoPkg/Library/OpensslLib/OpensslLibCrypto.inf | 2 +-
> EmulatorPkg/EmulatorPkg.dsc | 12 +-
> EmulatorPkg/Win/Host/WinHost.inf | 8 +-
> .../RegularExpressionDxe/RegularExpressionDxe.inf | 2 +-
> OvmfPkg/OvmfPkgIa32.dsc | 6 +-
> OvmfPkg/OvmfPkgIa32X64.dsc | 6 +-
> OvmfPkg/OvmfPkgX64.dsc | 6 +-
> 14 files changed, 111 insertions(+), 111 deletions(-)
>
> --
> 2.13.0.windows.1
>
>
>
>
prev parent reply other threads:[~2019-11-14 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 8:24 [Patch 0/5] Rename tool chain name CLANG9 to CLANGPDB Liming Gao
2019-11-14 8:24 ` [Patch 1/5] BaseTools: Rename tool chain " Liming Gao
2019-11-15 1:25 ` Bob Feng
2019-11-14 8:24 ` [Patch 2/5] MdeModulePkg RegularExpressionDxe: Update tool chain name " Liming Gao
2019-11-14 16:09 ` Wang, Jian J
2019-11-14 8:24 ` [Patch 3/5] CryptoPkg CryptoLib: " Liming Gao
2019-11-14 8:57 ` [edk2-devel] " Wang, Jian J
2019-11-14 8:24 ` [Patch 4/5] OvmfPkg DSC: " Liming Gao
2019-11-14 9:39 ` Laszlo Ersek
2019-11-14 8:24 ` [Patch 5/5] EmulatorPkg DSC and WinHost.inf: " Liming Gao
2019-11-14 8:44 ` Ni, Ray
2019-11-14 14:44 ` Leif Lindholm [this message]
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=20191114144441.GH7323@bivouac.eciton.net \
--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