From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: davids@webmaster.com
Cc: <Valdis.Kletnieks@vt.edu>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Ingo Molnar" <mingo@elte.hu>,
"Arnaldo Carvalho de Melo" <acme@ghostprotocols.net>,
<linux-kernel@vger.kernel.org>, "Alan Cox" <alan@redhat.com>
Subject: Re: [PATCH] 2.6.25-rc2-mm1 - fix mcount GPL bogosity.
Date: Tue, 26 Feb 2008 12:29:32 +0000 [thread overview]
Message-ID: <20080226122932.5f83d6d4@core> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKGEKDKKAC.davids@webmaster.com>
> I don't know who told you that or why, but it's obvious nonsense, as this
> issue shows. Exports should be marked GPL if and only if they cannot be used
> except in a derivative work. If it is possible to use them without taking
> sufficient protectable expression, they should not be marked GPL.
>
> This was what everyone agreed to when GPL exports were created.
No it wasn't.
Alan
next prev parent reply other threads:[~2008-02-26 12:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 17:59 [PATCH] 2.6.25-rc2-mm1 - fix mcount GPL bogosity Valdis.Kletnieks
2008-02-25 18:23 ` Steven Rostedt
2008-02-25 18:19 ` Alan Cox
2008-02-25 19:27 ` Adrian Bunk
2008-02-25 19:48 ` Alan Cox
2008-02-25 20:09 ` Adrian Bunk
2008-02-25 20:38 ` Alan Cox
2008-02-25 21:17 ` Valdis.Kletnieks
2008-02-26 1:30 ` David Schwartz
2008-02-26 12:29 ` Alan Cox [this message]
2008-02-26 15:43 ` Krzysztof Halasa
2008-02-26 17:04 ` Krzysztof Halasa
2008-02-26 17:21 ` Alan Cox
2008-02-26 17:44 ` Krzysztof Halasa
2008-02-26 18:04 ` Alan Cox
2008-02-26 18:19 ` David Schwartz
2008-02-26 23:13 ` Krzysztof Halasa
2008-02-26 23:35 ` David Schwartz
2008-02-27 0:05 ` Krzysztof Halasa
2008-02-27 0:28 ` David Schwartz
2008-02-27 10:31 ` Alan Cox
2008-02-27 10:55 ` Krzysztof Halasa
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=20080226122932.5f83d6d4@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Valdis.Kletnieks@vt.edu \
--cc=acme@ghostprotocols.net \
--cc=akpm@linux-foundation.org \
--cc=alan@redhat.com \
--cc=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.