Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Dengke Du <dengke.du@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] avahi: upgrade to 0.7
Date: Tue, 31 Oct 2017 14:44:15 +0800	[thread overview]
Message-ID: <cover.1509431793.git.dengke.du@windriver.com> (raw)

The following changes since commit 65d23bd7986615fdfb0f1717b615534a2a14ab80:

  README.qemu: qemuppc64 is not supported (2017-10-16 23:54:31 +0100)

are available in the git repository at:

  https://github.com/DengkeDu/openembedded-core.git dengke/avahi-0.7
  https://github.com//tree/dengke/avahi-0.7

Dengke Du (1):
  avahi: upgrade to 0.7

 .../avahi/{avahi-ui_0.6.32.bb => avahi-ui_0.7.bb}  |  6 ++---
 meta/recipes-connectivity/avahi/avahi.inc          | 11 +++-----
 .../avahi/{avahi_0.6.32.bb => avahi_0.7.bb}        |  6 ++---
 ...c-install-GtkBuilder-interface-files-for-.patch | 29 ---------------------
 .../files/avahi-fix-resource-unavaiable.patch      | 30 ----------------------
 5 files changed, 7 insertions(+), 75 deletions(-)
 rename meta/recipes-connectivity/avahi/{avahi-ui_0.6.32.bb => avahi-ui_0.7.bb} (89%)
 rename meta/recipes-connectivity/avahi/{avahi_0.6.32.bb => avahi_0.7.bb} (78%)
 delete mode 100644 meta/recipes-connectivity/avahi/files/0001-configure.ac-install-GtkBuilder-interface-files-for-.patch
 delete mode 100644 meta/recipes-connectivity/avahi/files/avahi-fix-resource-unavaiable.patch

-- 
2.7.4



             reply	other threads:[~2017-10-31  6:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31  6:44 Dengke Du [this message]
2017-10-31  6:44 ` [PATCH 1/1] avahi: upgrade to 0.7 Dengke Du
2017-10-31 19:20   ` Khem Raj
2017-11-01  1:35     ` Dengke Du
2017-11-01  1:54       ` Khem Raj

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.1509431793.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox