All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Fruhwirth Clemens <clemens@endorphin.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, 4 Aug 2004 12:56:20 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0408041251060.24588@ppc970.osdl.org> (raw)
In-Reply-To: <1091647612.24215.12.camel@ghanima>



On Wed, 4 Aug 2004, Fruhwirth Clemens wrote:
> 
> 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.

Ahh. Fair enough. I didn't have any lawyer look at it, I just don't like 
assuming.

> 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.

I'd much rather do the social work, not so much necessarily for legal 
reasons, but for my own menal well-being. It's just _so_ much nicer to 
work with a code-base where none of the authors might complain about being 
included.

So even if the original license is GPL-compatible, just the fact that Jari 
doesn't want his work re-licensed means that I don't want his work in the 
kernel - whether it's a legal issue or not. 

Now, I obviously believe that Jari has acted like an ass, since he has
used the very same code under the GPL before, but hey, that's his problem. 

Jari - please stop distributing your loop-aes patches. If you consider the 
license to be non-GPL-compatible, then you have no business distributing 
the thing as kernel patches. Alternatively, just say it's GPL'd. You can't 
have it both ways.

		Linus

  reply	other threads:[~2004-08-04 19:56 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
2004-08-04 19:56           ` Linus Torvalds [this message]
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=Pine.LNX.4.58.0408041251060.24588@ppc970.osdl.org \
    --to=torvalds@osdl.org \
    --cc=clemens@endorphin.org \
    --cc=davem@redhat.com \
    --cc=jariruusu@users.sourceforge.net \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.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 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.