From: John Snow <jsnow@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>,
qemu devel list <qemu-devel@nongnu.org>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>
Subject: Re: [PATCH v2 0/2] edk2 build scripts: eliminate python 2 dependency
Date: Fri, 20 Sep 2019 12:06:41 -0400 [thread overview]
Message-ID: <364077b0-455a-b65a-dbc8-a8b0409c287e@redhat.com> (raw)
In-Reply-To: <20190920083808.21399-1-lersek@redhat.com>
On 9/20/19 4:38 AM, Laszlo Ersek wrote:
> v1 URL:
> http://mid.mail-archive.com/20190918171141.15957-1-lersek@redhat.com
>
> Updates are noted on each patch.
>
> Cc: Eduardo Habkost <ehabkost@redhat.com>
> Cc: John Snow <jsnow@redhat.com>
> Cc: Philippe Mathieu-Daudé <philmd@redhat.com>
>
> Thanks
> Laszlo
>
> Laszlo Ersek (2):
> edk2 build scripts: honor external BaseTools flags with
> uefi-test-tools
> edk2 build scripts: work around TianoCore#1607 without forcing Python
> 2
>
> roms/Makefile | 1 +
> roms/edk2-build.sh | 4 ++--
> roms/edk2-funcs.sh | 17 +++++++++++++++++
> tests/uefi-test-tools/Makefile | 5 ++++-
> tests/uefi-test-tools/build.sh | 6 ++++--
> 5 files changed, 28 insertions(+), 5 deletions(-)
>
Thank you again!
I'm sure we'll find all of the rough spots during the rc process, so I
am quite content for now.
Reviewed-by: John Snow <jsnow@redhat.com>
next prev parent reply other threads:[~2019-09-20 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 8:38 [PATCH v2 0/2] edk2 build scripts: eliminate python 2 dependency Laszlo Ersek
2019-09-20 8:38 ` [PATCH v2 1/2] edk2 build scripts: honor external BaseTools flags with uefi-test-tools Laszlo Ersek
2019-09-20 8:43 ` Philippe Mathieu-Daudé
2019-09-20 8:38 ` [PATCH v2 2/2] edk2 build scripts: work around TianoCore#1607 without forcing Python 2 Laszlo Ersek
2019-09-20 8:42 ` Philippe Mathieu-Daudé
2019-09-20 16:06 ` John Snow [this message]
2019-09-24 15:28 ` [PATCH v2 0/2] edk2 build scripts: eliminate python 2 dependency Philippe Mathieu-Daudé
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-all 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=364077b0-455a-b65a-dbc8-a8b0409c287e@redhat.com \
--to=jsnow@redhat.com \
--cc=ehabkost@redhat.com \
--cc=lersek@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).