Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Cristian Iorga <cristian.iorga@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] glib-2.0 and bluez5 upgrades
Date: Wed, 23 Oct 2013 19:59:37 +0300	[thread overview]
Message-ID: <cover.1382547468.git.cristian.iorga@intel.com> (raw)

The following changes since commit ffb440c37c3491fa5d9a1408341f7c15eacdc9ce:

  midori: exclude from self-hosted for mips64 (2013-10-23 07:18:54 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib ciorga/PU2
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=ciorga/PU2

Cristian Iorga (2):
  glib-2.0: upgrade to 2.38.1
  bluez5: upgrade to 5.10

 .../bluez5/{bluez5-5.7 => bluez5-5.10}/bluetooth.conf                | 0
 meta/recipes-connectivity/bluez5/bluez5_5.10.bb                      | 5 +++++
 meta/recipes-connectivity/bluez5/bluez5_5.7.bb                       | 5 -----
 .../recipes-core/glib-2.0/{glib-2.0_2.38.0.bb => glib-2.0_2.38.1.bb} | 4 ++--
 4 files changed, 7 insertions(+), 7 deletions(-)
 rename meta/recipes-connectivity/bluez5/{bluez5-5.7 => bluez5-5.10}/bluetooth.conf (100%)
 create mode 100644 meta/recipes-connectivity/bluez5/bluez5_5.10.bb
 delete mode 100644 meta/recipes-connectivity/bluez5/bluez5_5.7.bb
 rename meta/recipes-core/glib-2.0/{glib-2.0_2.38.0.bb => glib-2.0_2.38.1.bb} (93%)

-- 
1.8.1.2



             reply	other threads:[~2013-10-23 16:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-23 16:59 Cristian Iorga [this message]
2013-10-23 16:59 ` [PATCH 1/2] glib-2.0: upgrade to 2.38.1 Cristian Iorga
2013-10-23 16:59 ` [PATCH 2/2] bluez5: upgrade to 5.10 Cristian Iorga
2013-10-29 16:59 ` [PATCH 0/2] glib-2.0 and bluez5 upgrades Iorga, Cristian

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=cover.1382547468.git.cristian.iorga@intel.com \
    --to=cristian.iorga@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