From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: chris_larson@mentor.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] classes/patch: optionally return non-patch sources
Date: Fri, 03 Feb 2012 16:51:50 +0000 [thread overview]
Message-ID: <1328287910.16474.5.camel@ted> (raw)
In-Reply-To: <1328122541-27434-2-git-send-email-bruce.ashfield@windriver.com>
On Wed, 2012-02-01 at 13:55 -0500, Bruce Ashfield wrote:
> commit:
>
> patch.bbclass: abstract out logic that determines patches to apply
>
> gives the ability for other clases to emit series files for use outside
> of a build system, or even within the build system. There are sometimes
> elements on the SRC_URI that while not directly applicable to patching,
> can be related to patching the package. For example, the yocto kernel
> class would like to know about these other source items on the SRC_URI
> to locate out of tree kernel features.
>
> This change keeps the default behaviour of returning patches, but adds the
> ability to request that non-patch results be returned. Additional filtering
> within the non-patch category, is left up to the caller of the routine.
>
> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
> ---
> meta/classes/patch.bbclass | 9 ++++++++-
> 1 files changed, 8 insertions(+), 1 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-02-03 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 18:55 [v2 PATCH 0/1] classes/patch: return non-patch source items Bruce Ashfield
2012-02-01 18:55 ` [PATCH] classes/patch: optionally return non-patch sources Bruce Ashfield
2012-02-03 16:51 ` 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=1328287910.16474.5.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@windriver.com \
--cc=chris_larson@mentor.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