From: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] python3: Upgrade from 3.3.3 to 3.4.2 rebase
Date: Thu, 9 Apr 2015 15:41:35 -0500 [thread overview]
Message-ID: <cover.1428611618.git.alejandro.hernandez@linux.intel.com> (raw)
Rebased the previous submitted patch to upgrade Python from 3.3.3 to 3.4.2
The following changes since commit 7fb6a6e907e5803597b2e12ba7047c46e57dba26:
upstream_tracking.inc: Add no-update reason for gdk-pixbuf (2015-04-09 10:01:48 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib hsalejandro/py3upRebasedApril
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=hsalejandro/py3upRebasedApril
Alejandro Hernandez (1):
python3: Upgrade from 3.3.3 to 3.4.2
...on-3.3-manifest.inc => python-3.4-manifest.inc} | 126 +++++++--------
...on3-native_3.3.3.bb => python3-native_3.4.2.bb} | 17 +-
.../python/python3/04-default-is-optimized.patch | 39 ++---
...2-distutils-prefix-is-inside-staging-area.patch | 29 ++--
.../python3/avoid-ncursesw-include-path.patch | 30 ++--
.../python/python3/python-3.3-multilib.patch | 180 +++++++++++----------
.../python/{python3_3.3.3.bb => python3_3.4.2.bb} | 21 ++-
...te-manifest-3.3.py => generate-manifest-3.4.py} | 8 +-
8 files changed, 222 insertions(+), 228 deletions(-)
rename meta/recipes-devtools/python/{python-3.3-manifest.inc => python-3.4-manifest.inc} (50%)
rename meta/recipes-devtools/python/{python3-native_3.3.3.bb => python3-native_3.4.2.bb} (80%)
rename meta/recipes-devtools/python/{python3_3.3.3.bb => python3_3.4.2.bb} (93%)
rename scripts/contrib/python/{generate-manifest-3.3.py => generate-manifest-3.4.py} (98%)
--
1.9.1
next reply other threads:[~2015-04-09 20:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 20:41 Alejandro Hernandez [this message]
2015-04-09 20:41 ` [PATCH 1/1] python3: Upgrade from 3.3.3 to 3.4.2 Alejandro Hernandez
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.1428611618.git.alejandro.hernandez@linux.intel.com \
--to=alejandro.hernandez@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.