From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] libical: update to 2.0.0
Date: Thu, 28 Jan 2016 15:15:56 +0200 [thread overview]
Message-ID: <56AA148C.2050104@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LYFHTzv3vF0fz3VQ2sLFgBVfqKw4HO15cUJanCt76REbw@mail.gmail.com>
On 01/28/2016 03:13 PM, Burton, Ross wrote:
> Presumably although the ABI changed, the API is the same so bluez5 and
> so on still builds against libical 2?
Generally, when there is a scary-looking major version update like this,
it's a good idea to 'bitbake world'.
Alex
next prev parent reply other threads:[~2016-01-28 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 12:37 [PATCH 1/2] libical: update to 2.0.0 Maxin B. John
2016-01-28 12:37 ` [PATCH 2/2] connman: fix crash with iptables 1.6 Maxin B. John
2016-01-28 13:00 ` [PATCH 1/2] libical: update to 2.0.0 Burton, Ross
2016-01-28 13:13 ` Maxin B. John
2016-01-28 13:13 ` Burton, Ross
2016-01-28 13:15 ` Alexander Kanavin [this message]
2016-01-28 13:39 ` Maxin B. John
2016-01-28 13:40 ` Alexander Kanavin
2016-01-28 14:28 ` Burton, Ross
2016-01-28 13:32 ` Maxin B. John
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=56AA148C.2050104@linux.intel.com \
--to=alexander.kanavin@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 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.