From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH,V2 0/6] libtool 2.4 upgrade
Date: Sat, 9 Oct 2010 13:37:07 +0200 [thread overview]
Message-ID: <20101009113707.GP3163@jama> (raw)
In-Reply-To: <AANLkTikLT9ZRLbnbGQ17AN5u0TiXdweP7HKH-QuLBH_E@mail.gmail.com>
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>
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
next prev parent reply other threads:[~2010-10-09 11:37 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 [this message]
2010-10-09 14:31 ` Khem Raj
2010-10-09 15:15 ` Koen Kooi
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=20101009113707.GP3163@jama \
--to=martin.jansa@gmail.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.