From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] boost: Support enums in hash
Date: Fri, 28 Sep 2012 11:24:33 +0100 [thread overview]
Message-ID: <1348827873.15753.42.camel@ted> (raw)
In-Reply-To: <1348803644-20961-1-git-send-email-raj.khem@gmail.com>
On Thu, 2012-09-27 at 20:40 -0700, Khem Raj wrote:
> Fixes builds which were building fine with previous versions of boost
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> meta/recipes-support/boost/boost_1.51.0.bb | 6 ++-
> meta/recipes-support/boost/files/hash_enums.patch | 45 +++++++++++++++++++++
> 2 files changed, 49 insertions(+), 2 deletions(-)
> create mode 100644 meta/recipes-support/boost/files/hash_enums.patch
Merged to master, thanks.
Richard
next prev parent reply other threads:[~2012-09-28 10:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 3:40 [PATCH] boost: Support enums in hash Khem Raj
2012-09-28 3:40 ` [PATCH] flex,bison: Add nativesdk variants Khem Raj
2012-09-28 12:24 ` Otavio Salvador
2012-09-28 10:24 ` Richard Purdie [this message]
2012-09-28 10:24 ` [PATCH] boost: Support enums in hash Richard Purdie
2012-09-28 10:32 ` Phil Blundell
2012-09-28 13:41 ` Khem Raj
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=1348827873.15753.42.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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