From: "Gao, Liming" <liming.gao@intel.com>
To: "Zhu, Yonghong" <yonghong.zhu@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [Patch 0/3 V2] BaseTools: Fix some bugs about hash value enable
Date: Tue, 12 Dec 2017 09:57:52 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E190F6C@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1513063644-6040-1-git-send-email-yonghong.zhu@intel.com>
Reviewed-by: Liming Gao <liming.gao@intel.com>
>-----Original Message-----
>From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
>Yonghong Zhu
>Sent: Tuesday, December 12, 2017 3:27 PM
>To: edk2-devel@lists.01.org
>Subject: [edk2] [Patch 0/3 V2] BaseTools: Fix some bugs about hash value
>enable
>
>This patches fix some bugs about hash value enable feature.
>
>Yonghong Zhu (3):
> BaseTools: Not cache the .efi file location into build option
> BaseTools: back up the binary files when hash value is same
> BaseTools: enable hash value check for single module build
>
> BaseTools/Source/Python/AutoGen/AutoGen.py | 16 +++++++++++-----
> BaseTools/Source/Python/build/build.py | 10 +++++++++-
> 2 files changed, 20 insertions(+), 6 deletions(-)
>
>--
>2.6.1.windows.1
>
>_______________________________________________
>edk2-devel mailing list
>edk2-devel@lists.01.org
>https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2017-12-12 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 7:27 [Patch 0/3 V2] BaseTools: Fix some bugs about hash value enable Yonghong Zhu
2017-12-12 7:27 ` [Patch 1/3 V2] BaseTools: Not cache the .efi file location into build option Yonghong Zhu
2017-12-12 7:27 ` [Patch 2/3 V2] BaseTools: back up the binary files when hash value is same Yonghong Zhu
2017-12-12 7:27 ` [Patch 3/3 V2] BaseTools: enable hash value check for single module build Yonghong Zhu
2017-12-12 9:57 ` Gao, Liming [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=4A89E2EF3DFEDB4C8BFDE51014F606A14E190F6C@SHSMSX104.ccr.corp.intel.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