From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: Larry McVoy <lm@bitmover.com>
Cc: Karl <ktatgenhorst@earthlink.net>,
Erik Mouw <J.A.K.Mouw@its.tudelft.nl>,
linux-kernel@vger.kernel.org
Subject: Re: Kernel module ethics.
Date: Mon, 4 Mar 2002 15:07:30 +0100 (MET) [thread overview]
Message-ID: <200203041407.PAA20022@cave.bitwizard.nl> (raw)
In-Reply-To: <20020227181333.A25723@work.bitmover.com> from Larry McVoy at "Feb 27, 2002 06:13:33 pm"
Larry McVoy wrote:
> Like I said before, unless your code is potentially worth at least a
> million bucks, it's almost certainly not worth anything financially,
> so GPL it. If you think it could be worth $1M, isn't it worth $.015M
> to figure out your rights?
In the software world, there are a lot of people who (think that they)
have code worth $1M, but they dont have that money in the bank (yet).
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots.
* There are also old, bald pilots.
next prev parent reply other threads:[~2002-03-04 14:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 21:11 Kernel module ethics Allo! Allo!
2002-02-27 21:33 ` Cyrille Chepelov
2002-02-27 22:23 ` Richard B. Johnson
2002-02-28 0:51 ` Erik Mouw
2002-02-28 1:03 ` Karl
2002-02-28 2:03 ` Erik Mouw
2002-02-28 2:13 ` Larry McVoy
2002-02-28 1:38 ` Karl
2002-03-04 14:07 ` Rogier Wolff [this message]
2002-02-28 2:37 ` John Jasen
2002-02-28 3:59 ` Richard Thrapp
2002-02-28 17:52 ` Jeff V. Merkey
2002-03-01 0:22 ` Alan Cox
2002-02-28 1:20 ` Rik van Riel
2002-02-27 22:37 ` Greg KH
2002-02-28 9:42 ` Helge Hafting
2002-02-28 13:55 ` Reid Hekman
2002-02-28 16:04 ` Mark H. Wood
2002-02-28 18:31 ` David Lang
-- strict thread matches above, loose matches on Subject: below --
2002-02-27 21:57 Jesper Juhl
2002-02-28 12:05 Alexander Sandler
2002-03-01 0:53 ` Erik Mouw
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=200203041407.PAA20022@cave.bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=J.A.K.Mouw@its.tudelft.nl \
--cc=ktatgenhorst@earthlink.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.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 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.