From: Eli Carter <eli.carter@inet.com>
To: James Wilkinson <jwilkinson43@comcast.net>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: GPL and proprietary driver code
Date: Wed, 07 Aug 2002 09:24:18 -0500 [thread overview]
Message-ID: <3D512D92.2000606@inet.com> (raw)
In-Reply-To: 007501c23e19$5a2899f0$656afea9@nsisw.com
James Wilkinson wrote:
> Please let me know if this should be asked elsewhere - I wasn't sure what
> the most appropriate forum would be for licensing questions...
[snip]
> Can anyone give me a definitive answer, or perhaps point me to an
> authoritative source? I've read up on the GPL license, and it is my opinion
> that my source could be kept proprietary, but I'd like to get expert
> opinions before continuing on.
So talk to a lawyer...
Eli
--------------------. "If it ain't broke now,
Eli Carter \ it will be soon." -- crypto-gram
eli.carter(a)inet.com `-------------------------------------------------
next prev parent reply other threads:[~2002-08-07 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 13:50 GPL and proprietary driver code James Wilkinson
2002-08-07 14:24 ` Eli Carter [this message]
2002-08-07 17:40 ` Erez Zadok
2002-08-07 17:49 ` Paul Jimenez
-- strict thread matches above, loose matches on Subject: below --
2002-08-07 18:29 Bryan Henderson
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=3D512D92.2000606@inet.com \
--to=eli.carter@inet.com \
--cc=jwilkinson43@comcast.net \
--cc=linux-fsdevel@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.