From: Patrick Ohly <patrick.ohly@intel.com>
To: Ed Bartosh <ed.bartosh@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/6] wic: fix for #11017
Date: Thu, 23 Feb 2017 15:08:43 +0100 [thread overview]
Message-ID: <1487858923.11306.31.camel@intel.com> (raw)
In-Reply-To: <cover.1487690169.git.ed.bartosh@linux.intel.com>
On Tue, 2017-02-21 at 17:23 +0200, Ed Bartosh wrote:
> This patchset improves handling of wic native tool dependencies and
> fixes minor bugs in the wic code.
I haven't tested it, but the patches themselves look good to me. Thanks!
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
prev parent reply other threads:[~2017-02-23 14:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 15:23 [PATCH 0/6] wic: fix for #11017 Ed Bartosh
2017-02-21 15:23 ` [PATCH 1/6] wic: use 2 sysroots to find native executable Ed Bartosh
2017-02-21 15:23 ` [PATCH 2/6] wic: use image recipe sysroot as default Ed Bartosh
2017-02-21 15:23 ` [PATCH 3/6] wic: exec_native_cmd: improve debug message Ed Bartosh
2017-02-21 15:23 ` [PATCH 4/6] wic: exec_native_cmd: fix undefined variable error Ed Bartosh
2017-02-21 15:23 ` [PATCH 5/6] wic: add WKS_FILE_DEPENDS variable Ed Bartosh
2017-02-21 15:23 ` [PATCH 6/6] wic: raise WicError instead of calling logger.error Ed Bartosh
2017-02-22 16:38 ` [PATCH 0/6] wic: fix for #11017 Burton, Ross
2017-02-22 20:53 ` Ed Bartosh
2017-02-23 10:18 ` Ed Bartosh
2017-02-23 10:39 ` Ed Bartosh
2017-02-23 14:08 ` Patrick Ohly [this message]
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=1487858923.11306.31.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=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