From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Marko Lindqvist <cazfi74@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 00/12] Prepare recipes for automake-1.13 (batch #3)
Date: Wed, 16 Jan 2013 12:02:24 +0000 [thread overview]
Message-ID: <1358337744.8129.3.camel@ted> (raw)
In-Reply-To: <cover.1358250908.git.cazfi74@gmail.com>
On Tue, 2013-01-15 at 13:57 +0200, Marko Lindqvist wrote:
> As more and more packages seem to have automake-1.13 related problems,
> it's becoming clear that I cannot fix world alone. I'm about to fix
> packages in openembedded-core the way I've been doing, but for supporting
> unfixed packages in other layers it would make sense to patch our
> version of automake-1.13 to still support AM_CONFIG_HEADER (the most
> common problem by far). We can drop that patch once most of the world
> has been updated to versions that work without.
Agreed, this does sound like the sensible way to go for us for now. I
appreciate the work you're doing on this!
Cheers,
Richard
prev parent reply other threads:[~2013-01-16 12:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 11:57 [PATCH 00/12] Prepare recipes for automake-1.13 (batch #3) Marko Lindqvist
2013-01-16 12:02 ` Richard Purdie [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=1358337744.8129.3.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=cazfi74@gmail.com \
--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