From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Derek Straka <derek@asterius.io>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] python: Upgrade both python and python-native to 2.7.14
Date: Mon, 29 Jan 2018 22:18:30 +0000 [thread overview]
Message-ID: <1517264310.3090.15.camel@linuxfoundation.org> (raw)
In-Reply-To: <1517262541-8719-1-git-send-email-derek@asterius.io>
On Mon, 2018-01-29 at 16:49 -0500, Derek Straka wrote:
> Rebased:
> - python/01-use-proper-tools-for-cross-build.patch
> - python/fix-makefile-for-ptest.patch
> - python/parallel-makeinst-create-bindir.patch
>
> Removed Upstreamed Patch:
> - python/Don-t-use-getentropy-on-Linux.patch
>
> Updated license checksum for changes in the copyright date. The
> license
> terms remain unchanged
>
> Added an extra do_compile item to create the native pgen that no
> longer
> gets compiled by default
>
> Update the json manifest with the latest dependency set
>
> Signed-off-by: Derek Straka <derek@asterius.io>
Your patch was merged into master so if there are tweaks they need to
be in a patch against master now please.
Cheers,
Richard
next prev parent reply other threads:[~2018-01-29 22:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 21:49 [PATCH v2] python: Upgrade both python and python-native to 2.7.14 Derek Straka
2018-01-29 22:03 ` ✗ patchtest: failure for python: Upgrade both python and python-native to 2.7.14 (rev3) Patchwork
2018-01-29 22:18 ` Richard Purdie [this message]
2018-01-29 22:26 ` [PATCH v2] python: Upgrade both python and python-native to 2.7.14 Derek Straka
2018-01-29 23:56 ` Alejandro Enedino Hernandez Samaniego
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=1517264310.3090.15.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=derek@asterius.io \
--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.