From: Mark Hatle <mark.hatle@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] [jethro/master] Misc fixes
Date: Wed, 25 Nov 2015 16:17:59 -0600 [thread overview]
Message-ID: <56563397.4010605@windriver.com> (raw)
In-Reply-To: <CAJTo0LabcacC1K9SWicuFnNQ445Up7ah_g9tngggPdYOFcnRSg@mail.gmail.com>
On 11/25/15 3:26 PM, Burton, Ross wrote:
>
> On 25 November 2015 at 20:44, Mark Hatle <mark.hatle@windriver.com
> <mailto:mark.hatle@windriver.com>> wrote:
>
> The following fixes have been tested on Jethro, I believe they are
> also applicable on master.
>
>
> As we generally want to ensure fixes go to master before jethro, can you rebase
> these to master (at least 1 and 2 don't apply anymore).
Luckily master hasn't deviated much. But honestly, I don't have time to rebase
right now. Next week would likely be the earliest.
> Also is the python2 fix applicable to python3 too?
The python2 fix was derived from the fix python3 already had.
HOWEVER, we've found conditions where it breaks python2. So it should not be
applied.
There is still a host contamination issue that needs to be resolved, but I don't
have any idea of a fix.
> Ross
prev parent reply other threads:[~2015-11-25 22:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 20:44 [PATCH 0/3] [jethro/master] Misc fixes Mark Hatle
2015-11-25 20:44 ` [PATCH 1/3] allarch.bbclass: allarch packages are having their hashes altered by baselib Mark Hatle
2015-11-25 20:44 ` [PATCH 2/3] python: Fix cross compiling x86->x86 Mark Hatle
2015-11-25 20:44 ` [PATCH 3/3] package_manager.py: Avoid installing an empty package list Mark Hatle
2015-11-25 21:26 ` [PATCH 0/3] [jethro/master] Misc fixes Burton, Ross
2015-11-25 22:17 ` Mark Hatle [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-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=56563397.4010605@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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