public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fruhwirth Clemens <clemens-dated-1092511613.8d37@endorphin.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: James Morris <jmorris@redhat.com>,
	Jari Ruusu <jariruusu@users.sourceforge.net>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"David S. Miller" <davem@redhat.com>
Subject: Re: Linux 2.6.8-rc3 - BSD licensing
Date: Wed, 04 Aug 2004 21:26:52 +0200	[thread overview]
Message-ID: <1091647612.24215.12.camel@ghanima> (raw)
In-Reply-To: <Pine.LNX.4.58.0408041146070.24588@ppc970.osdl.org>

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

On Wed, 2004-08-04 at 20:51, Linus Torvalds wrote:
> On Wed, 4 Aug 2004, Fruhwirth Clemens wrote:
> > 
> > As a matter of principle I do not add additional restrictions as respect
> > for the original author's efforts. But James, David or Linus might do
> > that, and by accident choose these additional restrictions to be like
> > those of the GPL. I would understand such action as I'd would like to
> > see that every kernel code is protected by the GPL.
> 
> That's not actually what we did. I refused the code originally because I
> didn't feel that Gladman's license was a proper subset of the GPL. 

I don't view the FSF as sort of last instance, but just for the
protocol: The exact wording of this license is labeled 'GPL-compatible'
by the FSF. Imho, this makes it a subset.

> I only accepted it after dual-licensing under the GPL had been ok'd by Dr Brian
> Gladman himself.

Additional coding, no problem, but additional social work, I'd prefer
not to be involved with. As there is no legal requirement, such efforts
would just make a good appearance. But, hey, if someone volunteers to
sort out these problems, my modifications to aes-i586.S can be
relicensed under the GPL anytime, no problem.

-- 
Fruhwirth Clemens <clemens@endorphin.org>  http://clemens.endorphin.org

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-08-04 19:29 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-03 22:09 Linux 2.6.8-rc3 Linus Torvalds
2004-08-04 12:07 ` Jan De Luyck
2004-08-04 12:13   ` Karol Kozimor
2004-08-04 12:40   ` Erik Mouw
2004-08-05 15:10     ` OGAWA Hirofumi
2004-08-05 22:19       ` szonyi calin
2004-08-04 12:57   ` Gene Heskett
2004-08-04 12:44 ` Juergen Stuber
2004-08-04 13:37   ` Geert Uytterhoeven
2004-08-04 15:04 ` Jari Ruusu
2004-08-04 16:00   ` James Morris
2004-08-04 16:10     ` J. Bruce Fields
2004-08-04 16:27       ` Arjan van de Ven
2004-08-04 18:19         ` Patrick McFarland
2004-08-04 18:45           ` Linus Torvalds
2004-08-05 13:54             ` Patrick McFarland
2004-08-04 21:27         ` H. Peter Anvin
2004-08-04 18:37     ` Linux 2.6.8-rc3 - BSD licensing Fruhwirth Clemens
2004-08-04 18:51       ` Linus Torvalds
2004-08-04 19:26         ` Fruhwirth Clemens [this message]
2004-08-04 19:56           ` Linus Torvalds
2004-08-05 12:33             ` Jari Ruusu
2004-08-05 16:50               ` Linus Torvalds
2004-08-05 17:45                 ` Måns Rullgård
2004-08-05 20:21                   ` Alan Cox
2004-08-05 21:37                     ` Måns Rullgård
2004-08-05 21:08                       ` Alan Cox
2004-08-06  9:47                 ` Jari Ruusu
2004-08-06 16:39                   ` Linus Torvalds
2004-08-07 10:19                     ` Jari Ruusu
2004-08-07 10:38                       ` Patrick McFarland
2004-08-07 17:27                       ` Linus Torvalds
2004-08-05 12:32     ` Linux 2.6.8-rc3 Jari Ruusu
2004-08-04 16:23   ` Linus Torvalds
2004-08-05 15:04     ` [PATCH] Drop asm i586 AES code James Morris
2004-08-04 15:08 ` Linux 2.6.8-rc3 (compile stats) John Cherry
2004-08-04 18:52 ` [patch] 2.6.8-rc3: fix modular kernel with gcc 2.95 Adrian Bunk
2004-08-06 19:57 ` 2.6.8-rc3: MPT Fusion compile error with PROC_FS=n Adrian Bunk

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=1091647612.24215.12.camel@ghanima \
    --to=clemens-dated-1092511613.8d37@endorphin.org \
    --cc=davem@redhat.com \
    --cc=jariruusu@users.sourceforge.net \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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