From: Adrian Bunk <bunk@kernel.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: grundler@parisc-linux.org, kyle@mcmartin.ca, matthew@wil.cx,
linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, bdale@hp.com
Subject: Re: [2.6 patch] binfmt_som.c: add MODULE_LICENSE
Date: Mon, 11 Aug 2008 21:43:41 +0300 [thread overview]
Message-ID: <20080811184341.GA1880@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <20080811165644.B18F04DE6@hiauly1.hia.nrc.ca>
On Mon, Aug 11, 2008 at 12:56:43PM -0400, John David Anglin wrote:
> > The toplevel COPYING file of the kernel sources contains the exact
> > licence text for all files (including binfmt_som.c) in the kernel.
>
> The COPYING file contains the license text but it doesn't say clearly
> what the license applies to. The closest thing to this is the statement
>
> Also note that the GPL below is copyrighted by the Free Software
> Foundation, but the instance of code that it refers to (the Linux
> kernel) is copyrighted by me and others who actually wrote it.
>
> in the COPYING file. The applicability of the GPL is parenthetical.
> The HOWTO file is more specific, but a clear license statement at the
> top level of the "source" tree is missing.
There's a file named COPYING at the top level, and a file named README
at the top level that says:
WHAT IS LINUX?
...
It is distributed under the GNU General Public License - see the
accompanying COPYING file for more details.
The GPLv2 licence on the Linux kernel is generally agreed upon
(whether one likes it or not is a different question, but all
contributors are aware that it applies) and has even been successfully
enforced at court, which makes your attempts of finding a way to
possibly interpret it differently kinda strange.
> Dave
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-08-11 18:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 21:11 Adrian Bunk
2008-08-10 0:55 ` Grant Grundler
2008-08-10 1:00 ` Matthew Wilcox
2008-08-10 13:41 ` Bdale Garbee
2008-08-10 15:14 ` Matthew Wilcox
2008-08-11 0:05 ` Grant Grundler
2008-08-11 14:15 ` Bdale Garbee
2008-08-10 14:11 ` Adrian Bunk
2008-08-11 0:10 ` Grant Grundler
2008-08-11 10:46 ` Adrian Bunk
2008-08-11 14:56 ` John David Anglin
2008-08-11 15:51 ` Adrian Bunk
2008-08-11 16:56 ` John David Anglin
2008-08-11 18:43 ` Adrian Bunk [this message]
2008-08-11 17:11 ` Matthew Wilcox
2008-08-15 21:44 ` Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
2008-06-15 16:13 Adrian Bunk
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=20080811184341.GA1880@cs181140183.pp.htv.fi \
--to=bunk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bdale@hp.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=grundler@parisc-linux.org \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=matthew@wil.cx \
/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
all inboxes | Powered by JetHome®