From: Dengke Du <dengke.du@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH V2 0/1] expat: Upgrade to 2.2.3
Date: Fri, 11 Aug 2017 00:35:27 -0400 [thread overview]
Message-ID: <cover.1502425947.git.dengke.du@windriver.com> (raw)
The following changes since commit 5e4bd86130866d4a92fa7b0fa6d3628126dfdf91:
libinput: Upgrade 1.7.3 -> 1.8.1 (2017-08-09 09:38:25 +0100)
are available in the git repository at:
https://github.com/DengkeDu/openembedded-core.git dengke/expat-upgrade-to-2.2.3
https://github.com//tree/dengke/expat-upgrade-to-2.2.3
Khem Raj (1):
expat: Upgrade to 2.2.3
meta/recipes-core/expat/expat.inc | 1 +
meta/recipes-core/expat/expat/libtool-tag.patch | 18 ++++++++++++++++++
meta/recipes-core/expat/expat_2.2.1.bb | 5 -----
meta/recipes-core/expat/expat_2.2.3.bb | 4 ++++
4 files changed, 23 insertions(+), 5 deletions(-)
create mode 100644 meta/recipes-core/expat/expat/libtool-tag.patch
delete mode 100644 meta/recipes-core/expat/expat_2.2.1.bb
create mode 100644 meta/recipes-core/expat/expat_2.2.3.bb
--
2.8.1
next reply other threads:[~2017-08-11 4:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 4:35 Dengke Du [this message]
2017-08-11 4:35 ` [PATCH V2 1/1] expat: Upgrade to 2.2.3 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.1502425947.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