From: Joshua Watt <jpewhacker@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [RFC 0/3] Add wildcards to SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS
Date: Tue, 27 Feb 2018 16:47:50 -0600 [thread overview]
Message-ID: <20180227224753.30881-1-JPEWhacker@gmail.com> (raw)
Wildcard support in SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS allows the native
tools that were in a hardcoded list to be specified in layer.conf with
the other exclusions.
Joshua Watt (3):
sstatesig: Add recipe wildcard
ref-manual: Update documentation for SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS
sstatesig: Move hardcoded native tools
documentation/ref-manual/ref-variables.xml | 18 ++++++++++++++++++
meta/conf/layer.conf | 5 +++++
meta/lib/oe/sstatesig.py | 9 ++++-----
3 files changed, 27 insertions(+), 5 deletions(-)
--
2.14.3
next reply other threads:[~2018-02-27 22:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 22:47 Joshua Watt [this message]
2018-02-27 22:47 ` [RFC 1/3] sstatesig: Add recipe wildcard Joshua Watt
2018-02-27 22:47 ` [RFC 2/3] ref-manual: Update SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS Joshua Watt
2018-02-27 22:47 ` [RFC 3/3] sstatesig: Move hardcoded native tools Joshua Watt
2018-02-28 14:14 ` [RFC 0/3] Add wildcards to SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS Richard Purdie
2018-02-28 14:43 ` Joshua Watt
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=20180227224753.30881-1-JPEWhacker@gmail.com \
--to=jpewhacker@gmail.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