Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2 V2] Recipes upgrade
Date: Wed, 4 Jul 2018 10:47:39 +0800	[thread overview]
Message-ID: <cover.1530672257.git.liezhi.yang@windriver.com> (raw)

* V2:
  - Remove the ones already on master-next
  - Upgrade git to 2.18 rathar than 2.17
  - Fix nfs-utils' build with glibc, I had tested it with glibc, then musl in
    V1, but after I fixed it with musl, I forgot to test with glibc again, now
    I tested with both glibc and musl.

// Robert

The following changes since commit 59a0a05235d80c86251cf45d7142bfc57f2e70d2:

  multilib: Tweak previous cross-canadian multilib fix (2018-07-04 00:01:37 +0100)

are available in the git repository at:

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

Robert Yang (2):
  git: 2.16.1 -> 2.18.0
  nfs-utils: 2.1.1 -> 2.3.1

 ...gure-Allow-to-explicitly-disable-nfsidmap.patch |  40 -------
 ...nclude-stdint.h-for-UINT16_MAX-definition.patch |  27 -----
 .../nfs-utils-1.2.3-sm-notify-res_init.patch       |  37 ------
 .../nfs-utils/nfs-utils-musl-limits.patch          | 133 +++++++++++++++++++++
 .../nfs-utils/nfs-utils-musl-res_querydomain.patch |  22 ++++
 .../{nfs-utils_2.1.1.bb => nfs-utils_2.3.1.bb}     |  13 +-
 meta/recipes-devtools/git/git.inc                  |  12 +-
 meta/recipes-devtools/git/git_2.16.1.bb            |  11 --
 meta/recipes-devtools/git/git_2.18.0.bb            |  11 ++
 9 files changed, 175 insertions(+), 131 deletions(-)
 delete mode 100644 meta/recipes-connectivity/nfs-utils/nfs-utils/0001-configure-Allow-to-explicitly-disable-nfsidmap.patch
 delete mode 100644 meta/recipes-connectivity/nfs-utils/nfs-utils/0001-include-stdint.h-for-UINT16_MAX-definition.patch
 delete mode 100644 meta/recipes-connectivity/nfs-utils/nfs-utils/nfs-utils-1.2.3-sm-notify-res_init.patch
 create mode 100644 meta/recipes-connectivity/nfs-utils/nfs-utils/nfs-utils-musl-limits.patch
 create mode 100644 meta/recipes-connectivity/nfs-utils/nfs-utils/nfs-utils-musl-res_querydomain.patch
 rename meta/recipes-connectivity/nfs-utils/{nfs-utils_2.1.1.bb => nfs-utils_2.3.1.bb} (92%)
 delete mode 100644 meta/recipes-devtools/git/git_2.16.1.bb
 create mode 100644 meta/recipes-devtools/git/git_2.18.0.bb

-- 
2.7.4



             reply	other threads:[~2018-07-04  2:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-04  2:47 Robert Yang [this message]
2018-07-04  2:47 ` [PATCH 1/2] git: 2.16.1 -> 2.18.0 Robert Yang
2018-07-04  2:47 ` [PATCH 2/2] nfs-utils: 2.1.1 -> 2.3.1 Robert Yang
2018-07-04  8:55   ` Burton, Ross
2018-07-04  9:03     ` 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.1530672257.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