From: "Peter A. Bigot" <pab@pabigot.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 0/2] add conflicts for recipes incompatible with bluez5
Date: Thu, 04 Dec 2014 18:28:59 -0600 [thread overview]
Message-ID: <5480FC4B.2090709@pabigot.com> (raw)
In-Reply-To: <cover.1417031737.git.pab@pabigot.com>
Ping. These are independent of the RFC patches.
On 11/26/2014 02:06 PM, Peter A. Bigot wrote:
> The following changes since commit 34be57e7454ffe5f591cc0d7638bf41bb4377a61:
>
> meta-networking: update LAYERDEPENDS (2014-11-24 14:12:02 -0500)
>
> are available in the git repository at:
>
> git://git.openembedded.org/meta-openembedded-contrib pabigot/bluez5
> http://cgit.openembedded.org/cgit.cgi/meta-openembedded-contrib/log/?h=pabigot/bluez5
>
> Peter A. Bigot (2):
> obexd: conflict with bluez5
> obex-data-server: conflict with bluez5
>
> meta-gnome/recipes-connectivity/obex/obexd_0.48.bb | 2 ++
> meta-oe/recipes-connectivity/obex/obex-data-server_0.4.6.bb | 1 +
> 2 files changed, 3 insertions(+)
>
prev parent reply other threads:[~2014-12-05 0:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 20:06 [PATCH 0/2] add conflicts for recipes incompatible with bluez5 Peter A. Bigot
2014-11-26 20:06 ` [meta-gnome][PATCH 1/2] obexd: conflict " Peter A. Bigot
2014-11-26 20:06 ` [meta-oe][PATCH 2/2] obex-data-server: " Peter A. Bigot
2014-12-05 0:28 ` Peter A. Bigot [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=5480FC4B.2090709@pabigot.com \
--to=pab@pabigot.com \
--cc=openembedded-devel@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