From: Dengke Du <dengke.du@windriver.com>
To: <ross.burton@intel.com>, <openembedded-core@lists.openembedded.org>
Subject: [PATCH V2 0/2] dropbear, chrpath: reduce local pending patches
Date: Wed, 12 Jul 2017 22:19:16 -0400 [thread overview]
Message-ID: <cover.1499911992.git.dengke.du@windriver.com> (raw)
The following changes since commit 81498aac9560fbeaeb58eaada32ce80e0ea51628:
yocto-project-qs: Updated Next Steps list (2017-07-12 00:28:16 +0100)
are available in the git repository at:
https://github.com/DengkeDu/openembedded-core.git dengke/dropbear-chrpath-reduce-local-pending-patch
https://github.com//tree/dengke/dropbear-chrpath-reduce-local-pending-patch
Dengke Du (2):
dropbear: reduce local pending patches
chrpath: reduce local pending patches
.../dropbear/dropbear/0003-configure.patch | 13 +++++------
.../fix-libtomcrypt-libtommath-ordering.patch | 11 +++++-----
.../chrpath/chrpath/standarddoc.patch | 25 ++++++++++++++++------
3 files changed, 32 insertions(+), 17 deletions(-)
--
2.8.1
next reply other threads:[~2017-07-13 2:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 2:19 Dengke Du [this message]
2017-07-13 2:19 ` [PATCH V2 1/2] dropbear: reduce local pending patches Dengke Du
2017-07-13 2:19 ` [PATCH V2 2/2] chrpath: " 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.1499911992.git.dengke.du@windriver.com \
--to=dengke.du@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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