All of lore.kernel.org
 help / color / mirror / Atom feed
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][v3] license.bbclass parsing changes rebased sans debug
Date: Fri, 27 May 2011 23:36:43 +0100	[thread overview]
Message-ID: <1306535803.27470.309.camel@rex> (raw)
In-Reply-To: <4DE02216.1010003@intel.com>

On Fri, 2011-05-27 at 15:13 -0700, Elizabeth Flanagan wrote:
> Using python abstract syntax trees as a parser and an ast visitor class, I've
> begun the first steps to being able to put some sanity to license selection.
> 
> One note. License modifiers have traditionally been limited to the "or greater"
> modifier "+". I've added another modifier "with exceptions" for licenses that
> have no generic ie common-licenses/GPL-2,0-with-GCC-exception
> 
> The following changes since commit 62e3f0ff7b27d8beb21b4b226051c3db654ea4e4:
> 
>    License Field Cleanup: Non-standard field names (2011-05-27 18:27:22 +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: Sane Parsing of licenses

Merged to master, thanks.

Richard




  reply	other threads:[~2011-05-27 22:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-27 22:13 [PATCH 0/1][v3] license.bbclass parsing changes rebased sans debug Elizabeth Flanagan
2011-05-27 22:36 ` Richard Purdie [this message]
2011-05-28  7:45 ` Koen Kooi
2011-05-28  9:16 ` Koen Kooi
2011-05-28 13:21   ` Elizabeth Flanagan
2011-05-28 13:41     ` Koen Kooi
2011-05-28 16:55   ` Khem Raj
2011-05-28 17:54     ` Elizabeth Flanagan
2011-05-28 20:57       ` Khem Raj
2011-05-28 23:31         ` Elizabeth Flanagan
2011-05-28 18:19 ` Otavio Salvador

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=1306535803.27470.309.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 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.