From: Ben B <kernel@bb.cactii.net>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Anonymous User <anonymouslinuxuser@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: GPL Violation?
Date: Thu, 17 Aug 2006 11:38:42 +0200 [thread overview]
Message-ID: <20060817093842.GA21430@cactii.net> (raw)
In-Reply-To: <1155795251.4494.9.camel@laptopd505.fenrus.org>
Arjan van de Ven <arjan@infradead.org> uttered the following thing:
> On Wed, 2006-08-16 at 22:48 -0700, Anonymous User wrote:
> > I believe that new kernel modules will be written to support I/O
> > peripherals and perhaps other things. I don't know the details right
> > now. What I am trying to do is get an idea of what requirements there
> > are to make the source code available under the GPL.
>
>
> you should talk to a lawyer, not LKML.
Minor gripe here...
Whilst it's true that a lawyer should get involved with these things, I
think it's also perfectly reasonable for someone to ask for input from
LKML, /. or other interesting places.
OP may already be planning to speak to a lawyer, and just wants to take
tidbits of info/experiences/etc from others to help the lawyer's
research.
BB
next prev parent reply other threads:[~2006-08-17 9:41 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-17 5:48 GPL Violation? Anonymous User
2006-08-17 6:14 ` Arjan van de Ven
2006-08-17 9:38 ` Ben B [this message]
2006-08-17 12:02 ` linux-os (Dick Johnson)
2006-08-17 16:11 ` Stefan Richter
2006-08-17 19:21 ` James Courtier-Dutton
2006-08-17 23:26 ` Ian Stirling
2006-08-17 23:35 ` Sean
2006-08-17 23:35 ` Sean
2006-08-18 0:32 ` Alan Cox
2006-08-18 7:23 ` Xavier Bestel
2006-08-18 12:23 ` Ian Stirling
2006-08-18 9:04 ` Helge Hafting
2006-08-17 6:42 ` Patrick McFarland
2006-08-17 6:54 ` Arjan van de Ven
2006-08-17 7:32 ` Patrick McFarland
2006-08-17 8:02 ` Adrian Bunk
2006-08-17 9:03 ` Patrick McFarland
2006-08-18 17:56 ` Adrian Bunk
2006-08-17 12:39 ` Grzegorz Kulewski
2006-08-17 13:41 ` Alan Cox
2006-08-17 13:31 ` Grzegorz Kulewski
2006-08-17 15:52 ` Theodore Tso
2006-08-18 2:03 ` Chase Venters
2006-08-17 8:32 ` Stefan Richter
2006-08-17 9:36 ` Patrick McFarland
2006-08-17 11:25 ` Alan Cox
2006-08-17 11:48 ` Neil Brown
2006-08-17 9:37 ` David Woodhouse
2006-08-17 23:45 ` Ian Stirling
2006-08-18 8:28 ` David Woodhouse
2006-08-18 12:52 ` Ian Stirling
2006-08-18 8:53 ` Bernd Petrovitsch
2006-08-18 9:04 ` David Woodhouse
2006-08-18 9:15 ` Bernd Petrovitsch
2006-08-20 22:05 ` Andrea Arcangeli
2006-08-20 22:20 ` Arjan van de Ven
2006-08-18 9:51 ` David Schwartz
2006-08-18 16:52 ` Alan Cox
2006-08-18 22:42 ` David Schwartz
2006-08-19 10:48 ` David Greaves
2006-08-19 16:29 ` Patrick McFarland
2006-08-19 17:28 ` David Greaves
2006-08-19 11:30 ` Helge Hafting
2006-08-19 15:44 ` Michael Buesch
2006-08-19 23:01 ` David Schwartz
2006-08-20 3:20 ` Chase Venters
2006-08-21 7:58 ` Helge Hafting
2006-08-21 11:27 ` Stefan Richter
2006-08-21 13:06 ` Alan Cox
2006-08-21 14:59 ` Horst H. von Brand
2006-08-17 9:30 ` Alan Cox
2006-08-17 9:29 ` Patrick McFarland
2006-08-17 14:52 ` Helge Hafting
2006-08-17 14:58 ` Anonymous User
2006-08-17 15:52 ` Stefan Richter
2006-08-17 16:19 ` Michiel de Boer
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=20060817093842.GA21430@cactii.net \
--to=kernel@bb.cactii.net \
--cc=anonymouslinuxuser@gmail.com \
--cc=arjan@infradead.org \
--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.