From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] libiconv: Add recipes for 1.13.1
Date: Wed, 20 Jul 2011 00:26:49 +0100 [thread overview]
Message-ID: <1311118009.2344.33.camel@rex> (raw)
In-Reply-To: <1311100227-8624-2-git-send-email-raj.khem@gmail.com>
On Tue, 2011-07-19 at 11:30 -0700, Khem Raj wrote:
> Import 1.13.1 recipes from meta-oe
> share common code through libiconv.inc
The big question this triggers for me is "why"?
Deleting libtool.m4 certainly looks neater than this version of patching
it out. Is that do_configure hack still needed with libtool 2.4?
Cheers,
Richard
next prev parent reply other threads:[~2011-07-19 23:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 18:30 [PATCH 1/2] Revert "libiconv: add version 1.13.1" Khem Raj
2011-07-19 18:30 ` [PATCH 2/2] libiconv: Add recipes for 1.13.1 Khem Raj
2011-07-19 23:26 ` Richard Purdie [this message]
2011-07-20 4:38 ` Khem Raj
2011-07-20 9:08 ` Henning Heinold
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=1311118009.2344.33.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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