From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Request for branch merge
Date: Mon, 12 Apr 2010 19:47:24 +0200 [thread overview]
Message-ID: <hpvmbc$af$1@dough.gmane.org> (raw)
In-Reply-To: <1271090705.14344.16.camel@localhost.localdomain>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12-04-10 18:45, Joshua Lock wrote:
> On Mon, 2010-04-12 at 10:37 +0200, Koen Kooi wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 01-04-10 17:33, Richard Purdie wrote:
>>> I've been aware that Poky and OE have been diverging slightly and I'd
>>> like to correct this. There are some patches that I've promised for a
>>> while too such as the rename from do_populate_staging ->
>>> do_populate_sysroot.
>>>
>>> With some help from Joshua Lock, I have a branch I'd like to propose be
>>> merged into OE.dev:
>>>
>>> http://cgit.openembedded.org/cgit.cgi/openembedded/log/?h=rpurdie/work-in-progress
>>
>> Joshuas last 3 commits to poky seem to fix Toms issue with binconfig and
>> my issue with chrpath, which only leaves the cross staging lamangler
>> stuff to get fixed.
>
> I've just pushed an updated version of the tree with the recent Poky
> changes you have observed and a merge of the autotools.bbclass to get
> the lamangler stuff.
Thanks! I also like the CONFIGUREOPTS change you snuck in :)
> It builds a console-image fine here but the testing hasn't been
> stringent as of yet.
IIRC 'abiword' break if the cross lamangler isn't working, going to try
that now.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLw1yrMkyGM64RGpERAmH0AJ9tOYlZcBrCx6pHfZ+FDoLdRxhPvgCeK4VD
eujM8p1Ip0kO8Ldi3lZRHJQ=
=86n7
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-04-12 17:50 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 15:33 Request for branch merge Richard Purdie
2010-04-01 15:41 ` Tom Rini
2010-04-01 15:43 ` Tom Rini
2010-04-01 16:07 ` Richard Purdie
2010-04-01 16:45 ` Tom Rini
2010-04-01 18:09 ` Richard Purdie
2010-04-01 18:33 ` Tom Rini
2010-04-01 18:43 ` Richard Purdie
2010-04-01 16:05 ` Richard Purdie
2010-04-01 16:46 ` Tom Rini
2010-04-01 15:46 ` Khem Raj
2010-04-01 16:09 ` Richard Purdie
2010-04-01 16:18 ` Andrea Adami
2010-04-01 16:29 ` Richard Purdie
2010-04-01 16:37 ` Gary Thomas
2010-04-01 17:17 ` Joshua Lock
2010-04-01 17:55 ` Koen Kooi
2010-04-01 18:17 ` Richard Purdie
2010-04-01 20:03 ` Chris Larson
2010-04-01 20:34 ` Tom Rini
2010-04-01 21:08 ` Koen Kooi
2010-04-01 21:25 ` Tom Rini
2010-04-01 21:27 ` Philip Balister
2010-04-01 22:26 ` Tom Rini
2010-04-02 13:40 ` Koen Kooi
2010-04-02 14:35 ` Koen Kooi
2010-04-02 21:41 ` Richard Purdie
2010-04-03 7:21 ` Koen Kooi
2010-04-02 21:29 ` Richard Purdie
2010-04-03 7:23 ` Koen Kooi
2010-04-08 15:40 ` Joshua Lock
2010-04-03 13:24 ` Koen Kooi
2010-04-12 8:37 ` Koen Kooi
2010-04-12 15:59 ` Tom Rini
2010-04-12 16:46 ` Joshua Lock
2010-05-01 23:29 ` Richard Purdie
2010-05-03 16:46 ` Tom Rini
2010-05-04 18:10 ` Richard Purdie
2010-05-04 18:55 ` Tom Rini
2010-05-05 23:22 ` Richard Purdie
2010-05-05 23:30 ` Tom Rini
2010-04-12 16:45 ` Joshua Lock
2010-04-12 17:47 ` Koen Kooi [this message]
2010-04-12 20:55 ` Koen Kooi
2010-04-12 22:19 ` Koen Kooi
2010-04-13 3:46 ` Richard Purdie
2010-04-13 7:06 ` Koen Kooi
2010-05-01 23:28 ` Richard Purdie
2010-05-02 14:13 ` Koen Kooi
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='hpvmbc$af$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@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