Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: <kai.kang@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: [meta-networking][PATCH 0/2] Upgrade 2 packages
Date: Tue, 16 Aug 2016 14:57:09 +0800	[thread overview]
Message-ID: <20160816065711.5083-1-kai.kang@windriver.com> (raw)

From: Kai Kang <kai.kang@windriver.com>


Kai Kang (2):
  radvd: 2.11 -> 2.14
  libnftnl: 1.0.5 -> 1.0.6

 .../recipes-daemons/radvd/{radvd_2.11.bb => radvd_2.14.bb}            | 4 ++--
 .../recipes-filter/libnftnl/{libnftnl_1.0.5.bb => libnftnl_1.0.6.bb}  | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)
 rename meta-networking/recipes-daemons/radvd/{radvd_2.11.bb => radvd_2.14.bb} (12%)
 rename meta-networking/recipes-filter/libnftnl/{libnftnl_1.0.5.bb => libnftnl_1.0.6.bb} (70%)

-- 
2.9.3



             reply	other threads:[~2016-08-16  6:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-16  6:57 kai.kang [this message]
2016-08-16  6:57 ` [PATCH 1/2] radvd: 2.11 -> 2.14 kai.kang
2016-08-16  6:57 ` [PATCH 2/2] libnftnl: 1.0.5 -> 1.0.6 kai.kang

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=20160816065711.5083-1-kai.kang@windriver.com \
    --to=kai.kang@windriver.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