From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/6] remove unneeded python2 recipes
Date: Mon, 23 May 2016 20:25:36 -0700 [thread overview]
Message-ID: <cover.1464060246.git.liezhi.yang@windriver.com> (raw)
They were required by buildtools-tarball, now replaced by python3 ones.
// Robert
The following changes since commit d6241e4c94a0a72acfc57e96a59918c0b2146d65:
useradd: Fix infinite build loop (2016-05-23 10:33:39 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/py3
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/py3
Robert Yang (6):
packagegroup-self-hosted.bb: python-git -> python3-git
python-pexpect: remove it
python-async: remove it
python-smmap: remove it
python-gitdb: remove it
python-git: remove it
.../packagegroups/packagegroup-self-hosted.bb | 2 +-
meta/recipes-devtools/python/python-async.inc | 15 -------------
meta/recipes-devtools/python/python-async_0.6.2.bb | 5 -----
meta/recipes-devtools/python/python-git.inc | 21 ------------------
meta/recipes-devtools/python/python-git_1.0.2.bb | 8 -------
meta/recipes-devtools/python/python-gitdb.inc | 16 --------------
meta/recipes-devtools/python/python-gitdb_0.6.4.bb | 7 ------
.../python/python-pexpect_4.0.1.bb | 25 ----------------------
meta/recipes-devtools/python/python-smmap.inc | 19 ----------------
meta/recipes-devtools/python/python-smmap_0.9.0.bb | 5 -----
.../recipes-devtools/python/python3-async_0.6.2.bb | 16 +++++++++++++-
meta/recipes-devtools/python/python3-git_1.0.2.bb | 21 +++++++++++++++++-
.../recipes-devtools/python/python3-gitdb_0.6.4.bb | 17 ++++++++++++++-
.../recipes-devtools/python/python3-smmap_0.9.0.bb | 20 ++++++++++++++++-
14 files changed, 71 insertions(+), 126 deletions(-)
delete mode 100644 meta/recipes-devtools/python/python-async.inc
delete mode 100644 meta/recipes-devtools/python/python-async_0.6.2.bb
delete mode 100644 meta/recipes-devtools/python/python-git.inc
delete mode 100644 meta/recipes-devtools/python/python-git_1.0.2.bb
delete mode 100644 meta/recipes-devtools/python/python-gitdb.inc
delete mode 100644 meta/recipes-devtools/python/python-gitdb_0.6.4.bb
delete mode 100644 meta/recipes-devtools/python/python-pexpect_4.0.1.bb
delete mode 100644 meta/recipes-devtools/python/python-smmap.inc
delete mode 100644 meta/recipes-devtools/python/python-smmap_0.9.0.bb
--
2.8.0
next reply other threads:[~2016-05-24 3:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 3:25 Robert Yang [this message]
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
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=cover.1464060246.git.liezhi.yang@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.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