From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/7] implement wic ls/cp/rm for ext partitions
Date: Tue, 5 Sep 2017 14:54:35 +0300 [thread overview]
Message-ID: <cover.1504611134.git.ed.bartosh@linux.intel.com> (raw)
Hi,
This patchset implements listing directory contents, copying and removing
files on ext[2,3,4] partitions of partitioned images.
The following changes since commit ee5bce2d11e783c0921df47b629025a6b67c44bf:
kernel-dev: Removed bad reference for creating patches. (2017-09-02 00:52:49 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib ed/wip
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=ed/wip
Ed Bartosh (7):
wic: implement ext fs support for 'wic ls'
wic: implement ext fs support for 'wic cp'
wic: implement ext fs support for 'wic rm'
wic: update help content
wic: selftest: add test_wic_ls_ext test case
wic: selftest: add test_wic_cp_ext test case
wic: selftest: add test_wic_rm_ext test case
meta/lib/oeqa/selftest/cases/wic.py | 69 +++++++++++++++++++++++++++++++++++++
scripts/lib/wic/engine.py | 55 ++++++++++++++++++-----------
scripts/lib/wic/help.py | 64 +++++++++++++++++-----------------
3 files changed, 136 insertions(+), 52 deletions(-)
--
Regards,
Ed
next reply other threads:[~2017-09-05 11:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 11:54 Ed Bartosh [this message]
2017-09-05 11:54 ` [PATCH 1/7] wic: implement ext fs support for 'wic ls' Ed Bartosh
2017-09-05 11:54 ` [PATCH 2/7] wic: implement ext fs support for 'wic cp' Ed Bartosh
2017-09-05 11:54 ` [PATCH 3/7] wic: implement ext fs support for 'wic rm' Ed Bartosh
2017-09-05 11:54 ` [PATCH 4/7] wic: update help content Ed Bartosh
2017-09-05 11:54 ` [PATCH 5/7] wic: selftest: add test_wic_ls_ext test case Ed Bartosh
2017-09-05 11:54 ` [PATCH 6/7] wic: selftest: add test_wic_cp_ext " Ed Bartosh
2017-09-05 11:54 ` [PATCH 7/7] wic: selftest: add test_wic_rm_ext " Ed Bartosh
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.1504611134.git.ed.bartosh@linux.intel.com \
--to=ed.bartosh@linux.intel.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