From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 07/14] libelf: import from OE rev d4f0211e2078d5033ae0dee74664de5520d8392d
Date: Mon, 30 May 2011 13:35:59 +0200 [thread overview]
Message-ID: <irvvev$vsj$1@dough.gmane.org> (raw)
In-Reply-To: <20110530093039.GF18119@jama.jama.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 30-05-11 11:30, Martin Jansa wrote:
> On Mon, May 30, 2011 at 08:23:33AM +0200, Koen Kooi wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 30-05-11 07:30, Martin Jansa wrote:
>>> On Sun, May 29, 2011 at 06:48:55PM -0700, Khem Raj wrote:
>>>> On Sun, 2011-05-29 at 23:56 +0200, Martin Jansa wrote:
>>>>> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
>>>>
>>>> You do not need to import libelf recipe. oe-core provides libelf via
>>>> elfutils change the depending recipes to depend on elfutils instead.
>>>
>>> OK, thanks! Will test and update patch.
>>> koen: should I update patch in same branch or send new patch removing
>>> libelf and changing deps?
>>
>> updating the branch would be good enough for me.
>
> updated branch pushed
> libelf removed and ltrace DEPENDS updated and moved to recipes-devtools
> devmem2 removed from branch because it was already applied :)
I cherry-picked devmem2 since I needed it for something in meta-ti I had
already pushed :)
Anyway, the rest is in as well now.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFN44EeMkyGM64RGpERAp2sAKC43/IKsjZ5rP9PDLOHuxs9l1Z0NwCgoXm1
R10Mh9E8khV0LK9wkGZAOxk=
=mxOk
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-05-30 11:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-29 21:56 [meta-oe][PATCH 00/14] Pull request #13 Martin Jansa
2011-05-29 21:56 ` [meta-oe][PATCH 01/14] dbus-daemon-proxy: add LIC_FILES_CHKSUM and disable as-needed Martin Jansa
2011-05-29 21:56 ` [meta-oe][PATCH 02/14] s3c24xx-gpio, s3c64xx-gpio: add LIC_FILES_CHKSUM Martin Jansa
2011-05-29 21:56 ` [meta-oe][PATCH 03/14] devmem2: import from OE rev d4f0211e2078d5033ae0dee74664de5520d8392d Martin Jansa
2011-05-29 21:56 ` [meta-oe][PATCH 04/14] socat: " Martin Jansa
2011-05-29 21:56 ` [meta-oe][PATCH 05/14] mbuffer: " Martin Jansa
2011-05-29 21:56 ` [meta-oe][PATCH 06/14] nmon: " Martin Jansa
2011-05-29 21:56 ` [meta-oe][PATCH 07/14] libelf: " Martin Jansa
2011-05-30 1:48 ` Khem Raj
2011-05-30 5:30 ` Martin Jansa
2011-05-30 6:23 ` Koen Kooi
2011-05-30 9:30 ` Martin Jansa
2011-05-30 11:35 ` Koen Kooi [this message]
2011-05-29 21:56 ` [meta-oe][PATCH 08/14] ltrace: " Martin Jansa
2011-05-30 1:50 ` Khem Raj
2011-05-29 21:56 ` [meta-oe][PATCH 09/14] pxaregs: " Martin Jansa
2011-05-29 21:56 ` [meta-oe][PATCH 10/14] serial-utils: " Martin Jansa
2011-05-29 21:56 ` [meta-oe][PATCH 11/14] tcp-wrappers: " Martin Jansa
2011-05-29 21:56 ` [meta-oe][PATCH 12/14] nfs-utils: " Martin Jansa
2011-05-29 21:56 ` [meta-oe][PATCH 13/14] i2c-tools: " Martin Jansa
2011-05-29 21:56 ` [meta-oe][PATCH 14/14] tcpdump: " Martin Jansa
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='irvvev$vsj$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--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.