Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] udev-extraconf: change LICENSE to MIT
Date: Thu, 30 Aug 2012 11:06:07 +0200	[thread overview]
Message-ID: <20120830090607.GA31247@jama.jama.net> (raw)
In-Reply-To: <5861D2CF-C4A7-47E2-A355-C77DF52A2D3B@dominion.thruhere.net>

[-- Attachment #1: Type: text/plain, Size: 1477 bytes --]

On Tue, Jul 31, 2012 at 02:46:40PM +0200, Koen Kooi wrote:
> 
> Op 31 jul. 2012, om 13:26 heeft Richard Purdie <richard.purdie@linuxfoundation.org> het volgende geschreven:
> 
> > On Mon, 2012-07-30 at 21:01 +0200, Martin Jansa wrote:
> >> * original recipe added by RP in fc128ab1e4fec27d44cebfa690a9bc233eda0caf was saying GPL
> >> * later it was changed to GPLv2
> >> * COPYING.GPL was added to reflect that
> >> * meta-oe has similar recipe with MIT license and even more scripts, so lets change LICENSE here too
> >> 
> >> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> >> ---
> >> meta/recipes-core/udev/udev-extraconf/COPYING.GPL |  339 ---------------------
> >> meta/recipes-core/udev/udev-extraconf_1.0.bb      |    8 +-
> >> 2 files changed, 4 insertions(+), 343 deletions(-)
> >> delete mode 100644 meta/recipes-core/udev/udev-extraconf/COPYING.GPL
> > 
> > Er, I think we need to be a little more careful than this. Just because
> > you want something to be so, doesn't make it happen just like that...
> > 
> > Looking at the commit, I've just copied the license from the original
> > source which was a GPLv2 recipe (udev). Where did mount.blacklist come
> > from originally? Is there evidence its MIT licensed? How did meta-oe
> > conclude this was MIT licensed?
> 
> It was written for oe-classic -> MIT licensed

ping4, are some lawyers still working on this?

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2012-08-30  9:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-30 15:03 [PATCH] udev-extraconf: merge with udev-extra-rules from meta-oe Martin Jansa
2012-07-30 15:12 ` Martin Jansa
2012-07-30 17:42 ` Koen Kooi
2012-07-30 17:59   ` Martin Jansa
2012-07-30 19:01     ` [PATCH] udev-extraconf: change LICENSE to MIT Martin Jansa
2012-07-31 11:26       ` Richard Purdie
2012-07-31 11:37         ` Martin Jansa
2012-07-31 12:46         ` Koen Kooi
2012-08-30  9:06           ` Martin Jansa [this message]
2012-08-05 10:23 ` [PATCH] layer.conf: add udev-extraconf to SIGGEN_EXCLUDERECIPES_ABISAFE Martin Jansa

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=20120830090607.GA31247@jama.jama.net \
    --to=martin.jansa@gmail.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