From: Hans Reiser <reiser@namesys.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org,
Reiserfs developers mail-list <Reiserfs-Dev@namesys.com>
Subject: Re: Proposed ACPI Licensing change
Date: Sun, 08 Dec 2002 02:44:24 +0300 [thread overview]
Message-ID: <3DF287D8.3060004@namesys.com> (raw)
In-Reply-To: <EDC461A30AC4D511ADE10002A5072CAD04C7A57F@orsmsx119.jf.intel.com>
Thanks Linus. I don't think that I have any inherent moral right to
dual-license reiserfs, but it sure is pragmatic to do so, and the
courtesy of permitting me to do so is gratefully accepted from our
contributors.
A bit more than half of our income comes from the dual licensing, and
we'd not have survived to this date fiscally without it. If anyone on
the reiserfs team ever owns a Boxster;-) at sometime in the future, it
will be from dual-licensing to Apple, a storage appliance vendor, or the
like.
Hans
Linus Torvalds wrote:
>In article <20021207002405.GR2544@fs.tum.de>,
>Adrian Bunk <bunk@fs.tum.de> wrote:
>
>
>>You can't forbid people to send GPL-only patches, so if a person doesn't
>>want his patch under your looser license you can't enforce that he also
>>releases it under your looser license.
>>
>>
>
>That's true, but on the other hand we've had these dual-license things
>before (PCMCIA has been mentioned, but we've had reiserfs and a number
>of drivers like aic7xxx too), and I don't think I've _ever_ gotten a
>patch submission that disallowed the dual license.
>
>In fact, I don't think I'd even merge a patch where the submitter tried
>to limit dual-license code to a simgle license (it might happen with
>some non-maintained stuff where the original source of the dual license
>is gone, but if somebody tried to send me an ACPI patch that said "this
>is GPL only", then I just wouldn't take it).
>
>I suspect the same "refuse to accept license limiting patches" would be
>true of most kernel maintainers. At least to me a choice of license by
>the _original_ author is a hell of a lot more important than the
>technical legality of then limiting it to just one license.
>
>So yes, dual-license code can become GPL-only, but not in _my_ tree.
>
>Somebody else can go off and make their own GPL-only additions, and
>quite frankly I would find it so morally offensive to ignore the intent
>of the original author that I wouldn't take the code even if it was an
>improvement (and I've found that people who are narrow-minded about
>licenses are narrow-minded about other things too, so I doubt it _would_
>be an improvement).
>
> Linus
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
>
next prev parent reply other threads:[~2002-12-07 23:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-07 0:10 Proposed ACPI Licensing change Grover, Andrew
2002-12-07 0:24 ` Adrian Bunk
2002-12-07 0:36 ` David Schwartz
2002-12-07 20:07 ` Linus Torvalds
2002-12-09 19:39 ` H. Peter Anvin
2002-12-07 0:51 ` Christoph Hellwig
2002-12-07 2:16 ` Alan Cox
2002-12-07 9:58 ` Jeff Garzik
2002-12-07 17:46 ` Greg KH
2002-12-07 23:44 ` Hans Reiser [this message]
2002-12-09 18:59 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2002-12-07 1:06 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=3DF287D8.3060004@namesys.com \
--to=reiser@namesys.com \
--cc=Reiserfs-Dev@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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