public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Lehmann <pcg@schmorp.de>
To: Pavel Machek <pavel@suse.cz>
Cc: Nigel Cunningham <ncunningham@users.sourceforge.net>,
	Pavel Machek <pavel@ucw.cz>, Arjan van de Ven <arjanv@redhat.com>,
	Cameron Patrick <cameron@patrick.wattle.id.au>,
	Michael Frank <mhf@linuxmail.org>,
	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: Sun, 28 Mar 2004 01:43:41 +0100	[thread overview]
Message-ID: <20040328004341.GA9258@schmorp.de> (raw)
In-Reply-To: <20040325145639.GH1505@openzaurus.ucw.cz>

On Thu, Mar 25, 2004 at 03:56:39PM +0100, Pavel Machek <pavel@suse.cz> wrote:
> > 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).
> 
> So if Nigel takes the BSD license out and replaces it with GPL,
> thats okay with you?

Yes. I believe this was always possible, and should now be rather explicit
with the changes I made.

However, I do not endorse it nor can I see why this should be necessary,
as other parts of the kernel are distributed with dual licensing left
intact, and I don't see why lzf is special.

But, again, relicensing is now explicitly allowed, I am aware of the
fact that this means that one can replace the license with GPL-only and
explicitly allow this happen with or without my consent. This was a
conscious decision etc.. etc.. :)

I hope it'sclear now that relicensing can happen anytime if necessary,
regardless of what my opinion on this is. I also don't need any further
explanations (unless you want to) and would hope that this issue is now
solved and fixing/merging plans can now continue.

-- 
      -----==-                                             |
      ----==-- _                                           |
      ---==---(_)__  __ ____  __       Marc Lehmann      +--
      --==---/ / _ \/ // /\ \/ /       pcg@goof.com      |e|
      -=====/_/_//_/\_,_/ /_/\_\       XX11-RIPE         --+
    The choice of a GNU generation                       |
                                                         |

  reply	other threads:[~2004-03-28  0:44 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
2004-03-25 14:56           ` Pavel Machek
2004-03-28  0:43             ` Marc Lehmann [this message]
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=20040328004341.GA9258@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox