From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] license.bbclass: Fix for infinite recursion and bad license_type
Date: Sun, 29 May 2011 09:41:12 +0100 [thread overview]
Message-ID: <1306658472.27470.325.camel@rex> (raw)
In-Reply-To: <4DE192AF.2040103@intel.com>
On Sat, 2011-05-28 at 17:26 -0700, Elizabeth Flanagan wrote:
> - Fixing LicenseVisitor so it forks at a BitOr instead of infinitely checking the node.
> - Fixing the bad license_type syntax by lstriping it so it's valid python.
> - Moved the bb.warn that we're using a SPDXLICENSEMAP to a note.
>
> The following changes since commit 1169f1b066d0028bd2ef7915440450bd42ef165e:
>
> license.bbclass: Sane Parsing of licenses (2011-05-27 23:36:24 +0100)
>
> are available in the git repository at:
> git://git.pokylinux.org/poky-contrib eflanagan/common-licenses
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=eflanagan/common-licenses
>
> Beth Flanagan (1):
> license.bbclass: Infinite recursion of or nodes
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-05-29 8:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-29 0:26 [PATCH 0/1] license.bbclass: Fix for infinite recursion and bad license_type Elizabeth Flanagan
2011-05-29 8:41 ` 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=1306658472.27470.325.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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