From: Laszlo Ersek <lersek@redhat.com>
To: "Gao, Liming" <liming.gao@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "leif.lindholm@linaro.org" <leif.lindholm@linaro.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
Andrew Fish <afish@apple.com>,
"stephano.cetola@linux.intel.com"
<stephano.cetola@linux.intel.com>
Subject: Re: Revert BaseTools Python3 Migration has been done at 1ccc4d895dd8d659d016efcd6ef8a48749aba1d0
Date: Mon, 15 Oct 2018 12:53:22 +0200 [thread overview]
Message-ID: <3a690658-45e4-43b4-63c3-068c09f2fddd@redhat.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E339DDE@SHSMSX104.ccr.corp.intel.com>
On 10/15/18 02:43, Gao, Liming wrote:
> Hi, all
> With the community discussion, Python3 migration is the fundamental change. It requires every developer to install Python3. Before this migration, the well communication and wide verification must be done. But now, most people is not aware of this change, and not try it. So, Python3 migration is reverted and be moved to edk2-staging Python3 branch (https://github.com/tianocore/edk2-staging/tree/Python3). BaseTools has been reverted at commit 1ccc4d895dd8d659d016efcd6ef8a48749aba1d0. So, please update edk2 to the latest trunk, and continue to your work. There is no change now.
>
>
>
> Python3 migration will not in the near edk2-stable201811 release. I will add it for next edk2 stable release plan. If you have any comments or confuse, please let me know.
Thank you!
Laszlo
prev parent reply other threads:[~2018-10-15 10:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 0:43 Revert BaseTools Python3 Migration has been done at 1ccc4d895dd8d659d016efcd6ef8a48749aba1d0 Gao, Liming
2018-10-15 10:53 ` Laszlo Ersek [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=3a690658-45e4-43b4-63c3-068c09f2fddd@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