From: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] license.bbclass: Fix for infinite recursion and bad license_type
Date: Sat, 28 May 2011 17:26:23 -0700 [thread overview]
Message-ID: <4DE192AF.2040103@intel.com> (raw)
- 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
meta/classes/license.bbclass | 15 ++++++++-------
1 files changed, 8 insertions(+), 7 deletions(-)
next reply other threads:[~2011-05-29 0:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-29 0:26 Elizabeth Flanagan [this message]
2011-05-29 8:41 ` [PATCH 0/1] license.bbclass: Fix for infinite recursion and bad license_type Richard Purdie
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=4DE192AF.2040103@intel.com \
--to=elizabeth.flanagan@intel.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