Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/8] [jethro] Consolidated pull
Date: Mon, 28 Mar 2016 02:40:21 -0700	[thread overview]
Message-ID: <cover.1459157937.git.liezhi.yang@windriver.com> (raw)

The following changes since commit 4d879cb8d7384ac4a96f22c1664b8875f2d8f615:

  devtool: extract: update SRCTREECOVEREDTASKS for kernel (2016-03-20 10:22:55 +0000)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib rbt/jethro-next
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/jethro-next

Bill Randle (1):
  systemd: fix segfault on shutdown

Brad Mouring (2):
  busybox-1.23: Backport patch to fix zcip false-conflict
  busybox_git: Fix SRCREV

Javier Viguera (1):
  bluez5: allow D-Bus to spawn obexd in systems without systemd

Khem Raj (1):
  ruby-native: Depend on openssl-native

Li Xin (1):
  gcc-cross-canadian.inc: add INSANE_SKIP_ to avoid build warning

Ross Burton (1):
  cdrtools: update SRC_URI

Ulrich Ölmann (1):
  nfs-utils: bugfix: adjust name of statd service unit

 meta/recipes-connectivity/bluez5/bluez5.inc        |   1 +
 ...-obexd-without-systemd-in-the-user-sessio.patch |  63 +++++++++++++
 .../files/bugfix-adjust-statd-service-name.patch   |  34 +++++++
 .../nfs-utils/nfs-utils_1.3.1.bb                   |   1 +
 ...wrong-comparison-of-source-IP-with-our-IP.patch |  38 ++++++++
 meta/recipes-core/busybox/busybox_1.23.2.bb        |   1 +
 meta/recipes-core/busybox/busybox_git.bb           |   2 +-
 .../0023-backported-fixes-for-null-messages.patch  | 101 +++++++++++++++++++++
 meta/recipes-core/systemd/systemd_225.bb           |   1 +
 .../cdrtools/cdrtools-native_3.01a31.bb            |   2 +-
 meta/recipes-devtools/gcc/gcc-cross-canadian.inc   |   2 +
 meta/recipes-devtools/ruby/ruby.inc                |   2 +-
 12 files changed, 245 insertions(+), 3 deletions(-)
 create mode 100644 meta/recipes-connectivity/bluez5/bluez5/0001-Allow-using-obexd-without-systemd-in-the-user-sessio.patch
 create mode 100644 meta/recipes-connectivity/nfs-utils/files/bugfix-adjust-statd-service-name.patch
 create mode 100644 meta/recipes-core/busybox/busybox/0001-zcip-fix-wrong-comparison-of-source-IP-with-our-IP.patch
 create mode 100644 meta/recipes-core/systemd/systemd/0023-backported-fixes-for-null-messages.patch

-- 
2.7.4



             reply	other threads:[~2016-03-28  9:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-28  9:40 Robert Yang [this message]
2016-03-28  9:40 ` [PATCH 1/8] ruby-native: Depend on openssl-native Robert Yang
2016-03-28  9:40 ` [PATCH 2/8] bluez5: allow D-Bus to spawn obexd in systems without systemd Robert Yang
2016-03-28  9:40 ` [PATCH 3/8] busybox-1.23: Backport patch to fix zcip false-conflict Robert Yang
2016-03-28  9:40 ` [PATCH 4/8] busybox_git: Fix SRCREV Robert Yang
2016-03-28  9:40 ` [PATCH 5/8] nfs-utils: bugfix: adjust name of statd service unit Robert Yang
2016-03-28  9:40 ` [PATCH 6/8] systemd: fix segfault on shutdown Robert Yang
2016-03-28  9:40 ` [PATCH 7/8] gcc-cross-canadian.inc: add INSANE_SKIP_ to avoid build warning Robert Yang
2016-03-28  9:40 ` [PATCH 8/8] cdrtools: update SRC_URI Robert Yang

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.1459157937.git.liezhi.yang@windriver.com \
    --to=liezhi.yang@windriver.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