From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [2011.03-maintenance] Pull request #9
Date: Thu, 31 Mar 2011 11:43:21 -0700 [thread overview]
Message-ID: <4D94CB49.60008@mentor.com> (raw)
In-Reply-To: <in2gmn$ucl$1@dough.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/31/2011 11:21 AM, Koen Kooi wrote:
> On 31-03-11 18:43, Tom Rini wrote:
>> On 03/31/2011 06:58 AM, Koen Kooi wrote:
>>> Tom,
>
>>> Please pull the 5 commits from here:
>
>>> URI: git://dominion.thruhere.net/var/cache/git/openembedded.git
>>> Branch: 2011.03-maintenance
>
>>> Philip Balister (3):
>>> autoconf: Fix paths for scripts installed on the target.
>>> automake: Fix paths in scripts installed on target.
>>> qmake2: Define env var for strip. Convert to use INC_PR.
>
>>> Tom Rini (2):
>>> In a large number of patches, remove unneeded '..' in paths.
>>> tcl: Rework mips-tclstrtod.patch
>
>>> You can view the branch online at
>>> http://dominion.thruhere.net/git/cgit.cgi/openembedded/log/?h=2011.03-maintenance
>
>>> The ones from Philip fix the native toolchain and you know what your
>>> patches do :)
>
>> Actually, I want to NAK my own patches here. After pushing here (and
>> Mark Hatle pushing to oe-core) I ran into patchdir param which lets us
>> not have to do patches in do_configure (which is really kinda wrong).
>> Unfortunately I haven't had time yet to re-do my patches, but I'll try
>> and get to that today.
>
> Can you pull in the 3 from Philip or do you want me to send a new request?
New request please (and I got the rework of my own bits done).
- --
Tom Rini
Mentor Graphics Corporation
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJNlMtJAAoJEI4NMjfc3nJxh18H/RaWfPtDJjbiAZbxMtE14HKl
Fg4FUWr/I7pnts+u4wFdlTexDLKcWhENjLXcP6Vl5l0yCHXtrTqOuBJo7MS2B4+b
b5D78k1VozOtBhtj+GBFcjXuCwnioKvkAlnad57alDCVsxcXzXzTNGY5ztzFx3LN
/IGlVDe/kOzxuc830tNZ67q2AsNcLK+UPeZPcS2et8ncbcG5mrTGsj+NcZso5SO6
WsBsc+xH7TyTZLfmUuTlAUhQ48YnwbvGknWxv7U2dt03zDzxuo3Rt5BETpjbtTCQ
YP/HsHlTamIgGE56R6irZos95b5Ez86iZ+t/bWSSx9gvkL38yFiEBgFMo0Sv750=
=lbWP
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2011-03-31 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 13:58 [2011.03-maintenance] Pull request #9 Koen Kooi
2011-03-31 16:43 ` Tom Rini
2011-03-31 18:21 ` Koen Kooi
2011-03-31 18:43 ` Tom Rini [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=4D94CB49.60008@mentor.com \
--to=tom_rini@mentor.com \
--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 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.