From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Humberto Ibarra <humberto.ibarra.lopez@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] multiconfig.py: added testsuite for multiconfig
Date: Thu, 27 Jul 2017 22:12:13 +0100 [thread overview]
Message-ID: <1501189933.22282.170.camel@linuxfoundation.org> (raw)
In-Reply-To: <b042029a217b541e652776a7117a35c70c81f4e3.1501186507.git.humberto.ibarra.lopez@intel.com>
On Thu, 2017-07-27 at 15:18 -0500, Humberto Ibarra wrote:
> Multiconfig was not being tested at all. This adds a few basic
> tests for multiconfig, including globbing.
>
> [Yocto #11612]
>
> Signed-off-by: Humberto Ibarra <humberto.ibarra.lopez@intel.com>
If I run this selftest and I have some multiconfigs already in my build
directory, what happens to them?
Cheers,
Richard
next prev parent reply other threads:[~2017-07-27 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 20:18 [PATCH 0/1] multiconfig.py: added testsuite for multiconfig Humberto Ibarra
2017-07-27 20:18 ` [PATCH 1/1] " Humberto Ibarra
2017-07-27 21:12 ` Richard Purdie [this message]
2017-07-31 16:28 ` Ibarra Lopez, Humberto
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=1501189933.22282.170.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=humberto.ibarra.lopez@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