From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org, saul.wold@intel.com
Subject: Re: [PATCH 1/1] linux-yocto: support externalsrc builds
Date: Wed, 28 Mar 2012 10:12:06 +0100 [thread overview]
Message-ID: <1332925926.28414.190.camel@ted> (raw)
In-Reply-To: <51492db5e0226485b065e10fe41ecb9070a6f2d2.1332901487.git.bruce.ashfield@windriver.com>
On Tue, 2012-03-27 at 22:31 -0400, Bruce Ashfield wrote:
> There are a few extra task that modify the source tree that should
> be removed when externalsrc is inherited by a recipe that uses a
> linux-yocto tree.
>
> Adding those tasks to SRCTREECOVEREDTASKS means that they are skipped
> and externalsrc works as intended.
>
> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
> ---
> meta/classes/kernel-yocto.bbclass | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-03-28 9:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 2:31 [PATCH 0/1] linux-yocto: fix externalsrc builds Bruce Ashfield
2012-03-28 2:31 ` [PATCH 1/1] linux-yocto: support " Bruce Ashfield
2012-03-28 9:12 ` Richard Purdie [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=1332925926.28414.190.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=saul.wold@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