From: Robert Yang <liezhi.yang@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/6] remove unneeded python2 recipes
Date: Tue, 24 May 2016 11:38:24 +0800 [thread overview]
Message-ID: <5743CCB0.3030105@windriver.com> (raw)
In-Reply-To: <1551285.Qn0PiMd4j4@peggleto-mobl.ger.corp.intel.com>
Hi Paul,
On 05/24/2016 11:34 AM, Paul Eggleton wrote:
> Hi Robert,
>
> On Mon, 23 May 2016 20:25:36 Robert Yang wrote:
>> They were required by buildtools-tarball, now replaced by python3 ones.
>
> It's not so much that they are required by buildtools-tarball, they are
> required by various scripts that we have. When you say unneeded, I assume only
> on the python3 branch? In master python-git very definitely is still needed.
I'm afraid no, my previous patch had been merged on master branch,
so I think that python-git and others are not needed any more ?
commit 9f921676a7cfac93117788b8dfeff652dfd65134
Author: Robert Yang <liezhi.yang@windriver.com>
Date: Wed May 18 00:43:44 2016 -0700
buildtools-tarball: replace nativesdk-python with nativesdk-python3
(From OE-Core rev: 97b5b150b3d3e82a5a42c1ea4351eed60aba7906)
// Robert
>
> Cheers,
> Paul
>
next prev parent reply other threads:[~2016-05-24 3:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 3:25 [PATCH 0/6] remove unneeded python2 recipes Robert Yang
2016-05-24 3:25 ` [PATCH 1/6] packagegroup-self-hosted.bb: python-git -> python3-git Robert Yang
2016-05-24 3:25 ` [PATCH 2/6] python-pexpect: remove it Robert Yang
2016-05-24 3:25 ` [PATCH 3/6] python-async: " Robert Yang
2016-05-24 3:25 ` [PATCH 4/6] python-smmap: " Robert Yang
2016-05-24 3:25 ` [PATCH 5/6] python-gitdb: " Robert Yang
2016-05-24 3:25 ` [PATCH 6/6] python-git: " Robert Yang
2016-05-24 3:34 ` [PATCH 0/6] remove unneeded python2 recipes Paul Eggleton
2016-05-24 3:38 ` Robert Yang [this message]
2016-05-24 3:53 ` Paul Eggleton
2016-05-24 5:43 ` Robert Yang
2016-05-24 7:20 ` Richard Purdie
2016-05-24 18:06 ` Anders Darander
2016-05-25 1:18 ` Robert Yang
2016-05-25 12:48 ` alexander.kanavin
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=5743CCB0.3030105@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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