From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [wic][PATCH 0/6] wic: kickstart fixes
Date: Mon, 18 Jan 2016 14:22:40 +0200 [thread overview]
Message-ID: <cover.1453119482.git.ed.bartosh@linux.intel.com> (raw)
Hi,
This patchset includes usability fixes and error handling improvements
for new kickstart parser.
The following changes since commit a2f23fa62858b89850aab339ddec16dcf6026b37:
openssh: CVE-2016-1907 (2016-01-18 11:47:08 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib ed/wic/kickstart-fixes
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=ed/wic/kickstart-fixes
Ed Bartosh (6):
wic: add custom exception KickStartError
wic: catch KickStartError
wic: improve processing of parseing errors
wic: removed unused imports
wic: override ArgumentParser.error
wic: rename kickstarter.py -> ksparser.py
scripts/lib/wic/conf.py | 7 +++++--
scripts/lib/wic/{kickstart.py => ksparser.py} | 24 ++++++++++++++++++----
scripts/lib/wic/plugins/source/bootimg-efi.py | 2 +-
scripts/lib/wic/plugins/source/bootimg-pcbios.py | 2 +-
.../lib/wic/plugins/source/isoimage-isohybrid.py | 2 +-
.../lib/wic/plugins/source/rootfs_pcbios_ext.py | 1 -
6 files changed, 28 insertions(+), 10 deletions(-)
rename scripts/lib/wic/{kickstart.py => ksparser.py} (82%)
--
Regards,
Ed
next reply other threads:[~2016-01-18 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 12:22 Ed Bartosh [this message]
2016-01-18 12:22 ` [wic][PATCH 1/6] wic: add custom exception KickStartError Ed Bartosh
2016-01-18 12:22 ` [wic][PATCH 2/6] wic: catch KickStartError Ed Bartosh
2016-01-18 12:22 ` [wic][PATCH 3/6] wic: improve processing of parseing errors Ed Bartosh
2016-01-18 12:22 ` [wic][PATCH 4/6] wic: removed unused imports Ed Bartosh
2016-01-18 12:22 ` [wic][PATCH 5/6] wic: override ArgumentParser.error Ed Bartosh
2016-01-18 12:22 ` [wic][PATCH 6/6] wic: rename kickstarter.py -> ksparser.py 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.1453119482.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