Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Joe MacDonald <Joe_MacDonald@mentor.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking][PATCH 0/5] Networking fixes and upgrades
Date: Wed, 7 Jan 2015 14:12:26 -0500	[thread overview]
Message-ID: <20150107191225.GI10013@mentor.com> (raw)
In-Reply-To: <cover.1420454954.git.paul.eggleton@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 2035 bytes --]

Merged, thanks.
-J.

[[oe] [meta-networking][PATCH 0/5] Networking fixes and upgrades] On 15.01.05 (Mon 10:51) Paul Eggleton wrote:

> Fix a couple of issues in the ntp recipe reported by Philip Balister
> (the file locations patch was previously posted separately; this
> version is identical). Also upgrade a few recipes.
> 
> 
> The following changes since commit 2ea3a19a478c526baa04d6b9a9e8c9f42aae9d34:
> 
>   ctapi-common: Add new recipe (2014-12-31 16:38:22 +0100)
> 
> are available in the git repository at:
> 
>   git://git.openembedded.org/meta-openembedded-contrib paule/networking-fixes
>   http://cgit.openembedded.org/cgit.cgi/meta-openembedded-contrib/log/?h=paule/networking-fixes
> 
> Paul Eggleton (5):
>   ntp: fix file locations
>   ntp: add explicit perl dependency to ntp-utils package
>   mtr: update to 0.86
>   traceroute: update to 2.0.21
>   dnsmasq: update to 2.72
> 
>  .../recipes-support/dnsmasq/dnsmasq_2.71.bb        | 10 -------
>  .../recipes-support/dnsmasq/dnsmasq_2.72.bb        | 10 +++++++
>  .../recipes-support/mtr/files/configure.patch      | 12 ---------
>  .../recipes-support/mtr/files/no-gtk.patch         | 31 ----------------------
>  .../mtr/{mtr_0.82.bb => mtr_0.86.bb}               | 10 +++----
>  meta-networking/recipes-support/ntp/ntp_4.2.8.bb   | 22 +++++++--------
>  .../{traceroute_2.0.20.bb => traceroute_2.0.21.bb} |  6 ++---
>  7 files changed, 28 insertions(+), 73 deletions(-)
>  delete mode 100644 meta-networking/recipes-support/dnsmasq/dnsmasq_2.71.bb
>  create mode 100644 meta-networking/recipes-support/dnsmasq/dnsmasq_2.72.bb
>  delete mode 100644 meta-networking/recipes-support/mtr/files/configure.patch
>  delete mode 100644 meta-networking/recipes-support/mtr/files/no-gtk.patch
>  rename meta-networking/recipes-support/mtr/{mtr_0.82.bb => mtr_0.86.bb} (51%)
>  rename meta-networking/recipes-support/traceroute/{traceroute_2.0.20.bb => traceroute_2.0.21.bb} (89%)
> 
> -- 
> 1.9.3
> 
-- 
-Joe MacDonald.
:wq

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 501 bytes --]

      parent reply	other threads:[~2015-01-07 19:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 10:51 [meta-networking][PATCH 0/5] Networking fixes and upgrades Paul Eggleton
2015-01-05 10:51 ` [meta-networking][PATCH 1/5] ntp: fix file locations Paul Eggleton
2015-01-05 10:51 ` [meta-networking][PATCH 2/5] ntp: add explicit perl dependency to ntp-utils package Paul Eggleton
2015-01-05 10:51 ` [meta-networking][PATCH 3/5] mtr: update to 0.86 Paul Eggleton
2015-01-05 10:51 ` [meta-networking][PATCH 4/5] traceroute: update to 2.0.21 Paul Eggleton
2015-01-05 10:51 ` [meta-networking][PATCH 5/5] dnsmasq: update to 2.72 Paul Eggleton
2015-01-07 19:12 ` Joe MacDonald [this message]

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=20150107191225.GI10013@mentor.com \
    --to=joe_macdonald@mentor.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /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