From: "Puustinen, Ismo" <ismo.puustinen@intel.com>
To: "dmitry.rozhkov@linux.intel.com" <dmitry.rozhkov@linux.intel.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] boost: backport a regression fix for forgotten header
Date: Mon, 29 May 2017 09:11:16 +0000 [thread overview]
Message-ID: <1496049074.37734.1.camel@intel.com> (raw)
In-Reply-To: <20170515115432.27466-1-dmitry.rozhkov@linux.intel.com>
On Mon, 2017-05-15 at 14:54 +0300, Dmitry Rozhkov wrote:
> The v1.64 release has broken array serialization code with issues
> reported in
>
> https://svn.boost.org/trac/boost/ticket/12516
> https://github.com/bmwcarit/meta-ros/issues/505
>
> Backport the fix from boost::serialization's master.
This is pretty important patch -- Refkit doesn't compile with latest
oe-core without the patch.
Ismo
prev parent reply other threads:[~2017-05-29 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 11:54 [PATCH] boost: backport a regression fix for forgotten header Dmitry Rozhkov
2017-05-29 9:11 ` Puustinen, Ismo [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=1496049074.37734.1.camel@intel.com \
--to=ismo.puustinen@intel.com \
--cc=dmitry.rozhkov@linux.intel.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