From: John Cavan <johnc@damncats.org>
To: Aaron Lehmann <aaronl@vitelus.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Fwd: Copyright infringement in linux/drivers/usb/serial/keyspan*fw.h
Date: Fri, 25 May 2001 06:00:27 -0400 [thread overview]
Message-ID: <3B0E2D3B.EDC082A6@damncats.org> (raw)
In-Reply-To: <20010524213404.A22585@vitelus.com>
Not to sound dense, but what part of the GPL prohibits a piece of GPL'd
software from including non-GPL'd code? The GPL does explicitly state
that you can't include it's software in proprietary code, but I don't
recall seeing a provision that prohibits the other way around.
It may not be in the "spirit" of the GPL, but as a legal document, the
letter means more than the spirit in the final determination.
Sorry to intrude on this, but the thought just struck me. I could be
wrong in my remembrance.
John
next prev parent reply other threads:[~2001-05-25 10:00 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-25 4:34 Fwd: Copyright infringement in linux/drivers/usb/serial/keyspan*fw.h Aaron Lehmann
2001-05-25 4:55 ` Copyright for drivers- two SCSI HBA drivers Matthew Jacob
2001-05-25 5:07 ` Fwd: Copyright infringement in linux/drivers/usb/serial/keyspan*fw.h Greg KH
2001-05-28 2:10 ` Fwd: Copyright infringement in linux/drivers/usb/serial/keys Hugh Blemings
2001-05-25 10:00 ` John Cavan [this message]
2001-05-25 11:10 ` Fwd: Copyright infringement in linux/drivers/usb/serial/keyspan*fw.h Alan Cox
2001-05-25 16:17 ` Alan Cox
[not found] <Pine.BSF.4.21.0105242155540.4849-100000@beppo.feral.com>
2001-05-25 5:57 ` Aaron Lehmann
2001-05-25 6:26 ` Matthew Jacob
2001-05-25 6:31 ` Aaron Lehmann
[not found] <mailman.990765360.7016.linux-kernel2news@redhat.com>
2001-05-25 6:02 ` Pete Zaitcev
[not found] <200105250559.f4P5x80365151@saturn.cs.uml.edu>
2001-05-25 6:03 ` Aaron Lehmann
2001-05-25 6:34 ` Alexander Viro
2001-05-25 6:42 ` Aaron Lehmann
2001-05-25 6:58 ` Alexander Viro
2001-05-25 7:02 ` Andreas Jaeger
2001-05-25 7:05 ` Alexander Viro
2001-05-25 10:56 ` Erik Mouw
2001-05-25 11:56 ` Alexander Viro
2001-05-25 12:44 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2001-05-25 9:34 Adam J. Richter
2001-05-25 16:06 ` Doug Ledford
2001-05-25 10:36 Adam J. Richter
2001-05-25 17:02 Adam J. Richter
2001-05-25 17:23 ` Jacob Luna Lundberg
2001-05-25 18:30 ` Larry McVoy
2001-05-25 22:30 ` Aaron Lehmann
2001-05-26 1:43 ` Larry McVoy
2001-05-25 19:14 ` Doug Ledford
2001-05-26 2:34 Adam J. Richter
2001-05-26 2:38 ` Larry McVoy
2001-05-26 4:52 ` Jeff V. Merkey
2001-05-26 3:10 Adam J. Richter
2001-05-26 11:00 ` James Sutherland
2001-05-29 0:03 ` Jamie Lokier
2001-05-29 0:24 ` Alan Cox
2001-05-29 0:55 ` Jamie Lokier
2001-05-26 11:09 Adam J. Richter
2001-05-29 1:38 Adam J. Richter
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=3B0E2D3B.EDC082A6@damncats.org \
--to=johnc@damncats.org \
--cc=aaronl@vitelus.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox