linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Maitin-Shepard <jbms@attbi.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Additional clauses to GPL in network drivers
Date: Sun, 07 Dec 2003 22:11:47 -0500	[thread overview]
Message-ID: <87r7zg0zrg.fsf@jay.local.invalid> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKKELHIIAA.davids@webmaster.com> (David Schwartz's message of "Sun, 7 Dec 2003 18:32:54 -0800")

[-- Attachment #1: Type: text/plain, Size: 635 bytes --]

"David Schwartz" <davids@webmaster.com> writes:

> 	It occurs to me that it might not be a bad idea to have a short blurb that
> could be included in individual files that clarifies that the file is part
> of a GPL'd distribution but that's clear that it doesn't impose any
> additional restrictions. Here's a stab at such a notice just off the top of
> my head:

[snip]

I don't understand the desire for a notice that is clearly redundant.
Due to the nature of the GPL (version 1 or 2), licensing an entire work
under it is exactly equivalent to licensing all of the component parts
individually under it.

-- 
Jeremy Maitin-Shepard

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2003-12-08  3:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-07 15:15 Additional clauses to GPL in network drivers John Bradford
2003-12-07 16:15 ` Krzysztof Halasa
2003-12-08  8:32   ` John Bradford
2003-12-08  0:29 ` David Schwartz
2003-12-08  1:00 ` Alex Belits
2003-12-08  2:32 ` David Schwartz
2003-12-08  3:11   ` Jeremy Maitin-Shepard [this message]
2003-12-08  3:51     ` David Schwartz
2003-12-08  6:40       ` Shawn Willden
2003-12-08 20:57       ` Matthias Andree
2003-12-07 17:15 Xose Vazquez Perez

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=87r7zg0zrg.fsf@jay.local.invalid \
    --to=jbms@attbi.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;
as well as URLs for NNTP newsgroup(s).