From: Olof Johansson <olof.johansson@axis.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] base.bbclass: Don't warn about "invalid" PACKAGECONFIGs by default
Date: Thu, 30 Jul 2015 12:14:47 +0200 [thread overview]
Message-ID: <1438250482-sup-5358@axis.com> (raw)
In-Reply-To: <CAJTo0La3miv94cfGvYYu6sDDyzw0X7e7-E7yosuKQb6FiQW9Ug@mail.gmail.com>
Excerpts from Burton, Ross's message of 2015-07-30 11:53:39 +0200:
> Can you elaborate on what this approach you refer to is?
For some of our internal recipes, we export a list of PACKAGECONFIGs regardless
of their use in the recipe. This is to make sure the list is synchronized over
all the affected recipes.
--
olof johansson
next prev parent reply other threads:[~2015-07-30 10:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 9:43 [PATCH] base.bbclass: Don't warn about "invalid" PACKAGECONFIGs by default Olof Johansson
2015-07-30 9:53 ` Burton, Ross
2015-07-30 10:14 ` Olof Johansson [this message]
2015-07-30 10:08 ` Robert Yang
2015-07-30 11:24 ` Olof Johansson
2015-07-30 15:21 ` Robert Yang
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=1438250482-sup-5358@axis.com \
--to=olof.johansson@axis.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