From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH,V2 0/6] libtool 2.4 upgrade
Date: Sat, 09 Oct 2010 17:15:17 +0200 [thread overview]
Message-ID: <i8q0u5$2t8$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTim_=Bg0mP+QjTWfvkdQ-+Xrp86fjg8sq8=bZ4=v@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
You can add:
Acked-by: Koen Kooi <k-kooi@ti.com>
to all the patches in this series
On 09-10-10 16:31, Khem Raj wrote:
> On Sat, Oct 9, 2010 at 4:37 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
>> On Fri, Oct 08, 2010 at 03:21:03PM -0700, Chris Larson wrote:
>>>> Personally I'm in favour of merging into head. That way it gets
>>>> accepted easier and faster.
>>>>
>>>
>>> Agreed, I am as well. As the new libtool is opt-in, I don't see the harm,
>>> and it'll ensure that any issues which crop up with the compatibility get
>>> fixed asap.
>>
>> Khem: feel free to add
>> Acked-by: Martin Jansa <Martin.Jansa@gmail.com>
>>
>
> Thanks. Do I have other pseudo acks too in this thread. ?
> btw libtool folks are excited that OE is using the sysroot
> functionality my patch to libtool is being merged
>
> http://lists.gnu.org/archive/html/libtool-patches/2010-10/msg00022.html
>
> I am confident that any roadblocks we run into the libtool community
> will help us
> so we are in good spot.
>
> Thanks
> -Khem
>> --
>> Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMsIcFMkyGM64RGpERAmluAKCODuUg1xYz6+6PMJ8FFrmFGB7seQCgvcJZ
byUjDfN8DmnMkcPi8EisuQM=
=i0Hp
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-10-09 15:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 1:46 [PATCH,V2 0/6] libtool 2.4 upgrade Khem Raj
2010-10-07 1:46 ` [PATCH,V2 1/6] libtool-2.4: Add recipes for libtool 2.4 Khem Raj
2010-10-07 1:46 ` [PATCH,V2 2/6] bitbake.conf: Define LIBTOOL_HAS_SYSROOT Khem Raj
2010-10-07 1:46 ` [PATCH, V2 3/6] autotools.bbclass: Conditionally use autotools_prepackage_lamangler Khem Raj
2010-10-07 1:46 ` [PATCH, V2 4/6] cross.bbclass, staging.bbclass, utils.bbclass: Make sure that .la munging is not done for libtool > 2.4 Khem Raj
2010-10-07 1:46 ` [PATCH, V2 5/6] insane.bbclass: If LIBTOOL_HAS_SYSROOT is set then do not check for la insanity Khem Raj
2010-10-07 1:46 ` [PATCH, V2 6/6] gnutls_2.10.1.bb: Update to libtools 2.4 macros Khem Raj
2010-10-07 7:56 ` [PATCH,V2 0/6] libtool 2.4 upgrade Koen Kooi
2010-10-07 18:31 ` Khem Raj
2010-10-07 22:56 ` Graham Gower
2010-10-07 23:16 ` Graham Gower
2010-10-08 20:48 ` Frans Meulenbroeks
2010-10-08 22:21 ` Chris Larson
2010-10-09 10:37 ` Koen Kooi
2010-10-09 11:37 ` Martin Jansa
2010-10-09 14:31 ` Khem Raj
2010-10-09 15:15 ` Koen Kooi [this message]
2010-10-09 16:45 ` Frans Meulenbroeks
2010-10-11 13: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='i8q0u5$2t8$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