From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] python-native: correct prefix handling for oe-core sysroot layout
Date: Tue, 03 Jan 2012 18:01:05 +0000 [thread overview]
Message-ID: <1325613665.28005.25.camel@phil-desktop> (raw)
In-Reply-To: <20120103174717.GH3958@jama.jama.net>
On Tue, 2012-01-03 at 18:47 +0100, Martin Jansa wrote:
> Where did you get python-native_2.6.6?
>
> That was removed with 2.7.2 upgrade in
> commit b284e9a512860b8a8380be80f96cebce6b92ff80
> Author: Nitin A Kamble <nitin.a.kamble@intel.com>
> Date: Fri Oct 14 07:06:13 2011 +0000
>
> Cheers,
Ah yes, sorry, I made the patch against the wrong repository. 2.7.2
still seems to be broken in the same way, though. I'll rebase the patch
tomorrow and send a new one.
p.
next prev parent reply other threads:[~2012-01-03 18:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 17:39 [PATCH] python-native: correct prefix handling for oe-core sysroot layout Phil Blundell
2012-01-03 17:47 ` Martin Jansa
2012-01-03 18:01 ` Phil Blundell [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-04 17:10 Phil Blundell
2012-01-05 20:24 ` Saul Wold
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=1325613665.28005.25.camel@phil-desktop \
--to=philb@gnu.org \
--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