From: Marc Lehmann <pcg@schmorp.de>
To: Nigel Cunningham <ncunningham@users.sourceforge.net>,
Pavel Machek <pavel@ucw.cz>
Cc: Arjan van de Ven <arjanv@redhat.com>,
Cameron Patrick <cameron@patrick.wattle.id.au>,
Michael Frank <mhf@linuxmail.org>, Pavel Machek <pavel@suse.cz>,
Software Suspend - Mailing Lists
<swsusp-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Swsusp-devel] lzf license
Date: Thu, 25 Mar 2004 15:26:54 +0100 [thread overview]
Message-ID: <20040325142654.GA11633@schmorp.de> (raw)
In-Reply-To: <20040325114736.GA300@elf.ucw.cz> <1080166848.2628.3.camel@calvin.wpcb.org.au>
On Thu, Mar 25, 2004 at 10:20:48AM +1200, Nigel Cunningham <ncunningham@users.sourceforge.net> wrote:
> I'm not sure what the verdict is in the end. Do we need changes to the
> license? If so, could you send me a patch, Marc?
I have no idea. I made an offer on how to change the license, if that
isn't ok, I'd like to hear.
On Thu, Mar 25, 2004 at 12:47:37PM +0100, Pavel Machek <pavel@ucw.cz> wrote:
> Linking BSD w/o advertising with kernel is okay, but it would taint
> the kernel, and is bad idea w.r.t. patents, anyway. Dual BSD/GPL is
> better way to go.
Well, if there is any problem with relicensing the code as GPL, let me
know. I offered to change the license to make this smoother, but lots of
kernel code came from a bsd license and was relicensed before.
If there are problems with that, I'd like to hear. I see no point in
keeping the code out just because it isn't gpl, but I don't see a point
in making the original distribution dual licensed for no reason. (and, as
I said, there is lots of bsd-derived code in the kernel and I am _really_
keen on getting rid of any problems that forbid relicensing).
I am now back from the cebit and much more responsive, btw.
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / pcg@goof.com |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
next prev parent reply other threads:[~2004-03-25 14:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-22 9:18 Michael Frank
2004-03-22 9:40 ` [Swsusp-devel] (no subject) Cameron Patrick
2004-03-22 9:49 ` Arjan van de Ven
2004-03-22 10:02 ` LZF inclusion in kernel Michael Frank
2004-03-22 18:21 ` [Swsusp-devel] lzf license Marc Lehmann
2004-03-23 11:47 ` Arjan van de Ven
2004-03-25 15:02 ` Marc Lehmann
2004-03-24 22:20 ` Nigel Cunningham
2004-03-25 14:26 ` Marc Lehmann [this message]
2004-03-25 14:56 ` Pavel Machek
2004-03-28 0:43 ` Marc Lehmann
2004-03-22 10:15 ` [Swsusp-devel] (no subject) Pavel Machek
2004-03-25 15:18 ` Marc Lehmann
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=20040325142654.GA11633@schmorp.de \
--to=pcg@schmorp.de \
--cc=arjanv@redhat.com \
--cc=cameron@patrick.wattle.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mhf@linuxmail.org \
--cc=ncunningham@users.sourceforge.net \
--cc=pavel@suse.cz \
--cc=pavel@ucw.cz \
--cc=swsusp-devel@lists.sourceforge.net \
/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.