mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michael Frank" <mhf@linuxmail.org>
To: arjanv@redhat.com, "Cameron Patrick" <cameron@patrick.wattle.id.au>
Cc: pcg@goof.com, "Pavel Machek" <pavel@suse.cz>,
	"Software Suspend - Mailing Lists" 
	<swsusp-devel@lists.sourceforge.net>,
	"kernel list" <linux-kernel@vger.kernel.org>
Subject: LZF inclusion in kernel
Date: Mon, 22 Mar 2004 18:02:52 +0800	[thread overview]
Message-ID: <opr49cu2le4evsfm@smtp.pacific.net.th> (raw)
In-Reply-To: <1079948988.5296.8.camel@laptop.fenrus.com>

On Mon, 22 Mar 2004 10:49:48 +0100, Arjan van de Ven <arjanv@redhat.com> wrote:

> On Mon, 2004-03-22 at 10:40, Cameron Patrick wrote:
>
>> The licence so described looks to me the same as LZF's licence.
>
> however at least I would prefer the author to dual license it ANYWAY,
> because compression stuff generally is riddled with patents; the author
> GPL licensing it at least gives all users a license of the authors
> patents (if any).
>

Right, for  kernel side the BSD license is too "simplistic".

I like to see a ACPI style license.

Regards
Michael

  reply	other threads:[~2004-03-22 10:08 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     ` Michael Frank [this message]
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-22 10:15   ` [Swsusp-devel] (no subject) Pavel Machek
2004-03-25 14:26 ` [Swsusp-devel] lzf license Marc Lehmann
2004-03-25 14:56   ` Pavel Machek
2004-03-28  0:43     ` Marc Lehmann
2004-03-25 15:18 ` [Swsusp-devel] (no subject) 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=opr49cu2le4evsfm@smtp.pacific.net.th \
    --to=mhf@linuxmail.org \
    --cc=arjanv@redhat.com \
    --cc=cameron@patrick.wattle.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=pcg@goof.com \
    --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

Powered by JetHome