All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dengke Du <dengke.du@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] json-glib,dropbear: upgrade to new version
Date: Thu, 1 Jun 2017 05:38:40 -0400	[thread overview]
Message-ID: <cover.1496309470.git.dengke.du@windriver.com> (raw)

The following changes since commit bd063fa288b49b6e3ea77982d0ccc46610feb1ad:

  tune-mips32*.inc: use consistent comments across all three .inc files (2017-05-30 10:15:20 +0100)

are available in the git repository at:

  https://github.com/DengkeDu/openembedded-core.git dengke/json-glib_dropbear_upgrade
  https://github.com//tree/dengke/json-glib_dropbear_upgrade

Dengke Du (2):
  json-glib: upgrade 1.2.2 -> 1.2.8
  dropbear: upgrade 2016.74 -> 2017.75

 .../dropbear/support-out-of-tree-builds.patch      | 43 ----------------------
 meta/recipes-core/dropbear/dropbear_2016.74.bb     |  7 ----
 meta/recipes-core/dropbear/dropbear_2017.75.bb     |  5 +++
 .../{json-glib_1.2.2.bb => json-glib_1.2.8.bb}     |  4 +-
 4 files changed, 7 insertions(+), 52 deletions(-)
 delete mode 100644 meta/recipes-core/dropbear/dropbear/support-out-of-tree-builds.patch
 delete mode 100644 meta/recipes-core/dropbear/dropbear_2016.74.bb
 create mode 100644 meta/recipes-core/dropbear/dropbear_2017.75.bb
 rename meta/recipes-gnome/json-glib/{json-glib_1.2.2.bb => json-glib_1.2.8.bb} (82%)

-- 
2.8.1



             reply	other threads:[~2017-06-01  9:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-01  9:38 Dengke Du [this message]
2017-06-01  9:38 ` [PATCH 1/2] json-glib: upgrade 1.2.2 -> 1.2.8 Dengke Du
2017-06-01  9:38 ` [PATCH 2/2] dropbear: upgrade 2016.74 -> 2017.75 Dengke Du

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.1496309470.git.dengke.du@windriver.com \
    --to=dengke.du@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 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.