From: Joshua Watt <jpewhacker@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [RFC 0/3] Add wildcards to SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS
Date: Wed, 28 Feb 2018 08:43:01 -0600 [thread overview]
Message-ID: <1519828981.2806.95.camel@gmail.com> (raw)
In-Reply-To: <1519827267.3436.9.camel@linuxfoundation.org>
On Wed, 2018-02-28 at 14:14 +0000, Richard Purdie wrote:
> On Tue, 2018-02-27 at 16:47 -0600, Joshua Watt wrote:
> > 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.
>
> I was always reluctant to add wildcard support to this but it does
> make
> sense. It worked out ok in the testing I gave it. As we're at feature
> freeze, this would have to go in ASAP.
I was more worried about http://lists.openembedded.org/pipermail/openem
bedded-core/2018-February/147901.html, which looked like it already
landed in master-next (886ffabca). I have no problem waiting for the
next development cycle on this, unless someone *really* wants it.
>
> Cheers,
>
> Richard
prev parent reply other threads:[~2018-02-28 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 22:47 [RFC 0/3] Add wildcards to SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS Joshua Watt
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 [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=1519828981.2806.95.camel@gmail.com \
--to=jpewhacker@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.