archive mirror
 help / color / mirror / Atom feed
From: Matthias Andree <>
Subject: Re: Additional clauses to GPL in network drivers
Date: Mon, 8 Dec 2003 21:57:14 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sun, 07 Dec 2003, David Schwartz wrote:

> > 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.
> 	It is definitely redundant. The idea is that if a portion of the
> distribution ever winds up somewhere, the terms are still clear. For
> example, one often finds modified header files or implementation files
> available that don't contain a copy of the GPL or, for that matter, any
> indication that the files included are covered by the GPL.

I usually state in header files that are likely to be taken elsewhere
what license applies without copying the full license or excerpts
thereof into the header. That should be sufficient. There is no need and
no desire to have all possible variants of GPL summaries all over the

> 	For this reason, I think it makes sense for files to carry some indication
> that they are covered by the GPL. Look, for example, at

Too long-winded and IMHO too easily misunderstood. The GPL itself
contains a "how to apply..." (this license to your code) section, and I
see no reason for any deviation from the suggestions stated there.

Even a copyright line and "you may only redistribute this file in
concordance with the terms of the GNU General Public License, version
(whatever applies) (optional "or any later version clause") is
sufficient according to the GPL.

If people actually read the full COPYING file, there'd be no reason for
such stupid GPL "clarifications". Such are not necessary. If the file is
meant to be offered under more than one license (say, BSD "no ad clause
version"/GPL is found sometimes), then that is certainly doable without
GPL "clarifications". The GPL is clear.

Note: IANAL.

Matthias Andree

Encrypt your mail: my GnuPG key ID is 0x052E7D95

  parent reply	other threads:[~2003-12-08 20:57 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
2003-12-08  3:51     ` David Schwartz
2003-12-08  6:40       ` Shawn Willden
2003-12-08 20:57       ` Matthias Andree [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).