From: Auke Kok <sofar@foo-projects.org>
To: Trent Waddington <trent.waddington@gmail.com>
Cc: Jon Masters <jonathan@jonmasters.org>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: [PATCH] Ban module license tag string termination trick
Date: Thu, 01 Feb 2007 15:34:32 -0800 [thread overview]
Message-ID: <45C27908.1000202@foo-projects.org> (raw)
In-Reply-To: <3d57814d0702011430l43c03ae1uc950339b6700f859@mail.gmail.com>
Trent Waddington wrote:
> On 2/2/07, Jon Masters <jonathan@jonmasters.org> wrote:
>> Ok. I totally dig the *idea* here - I mean, this issue has been ongoing
>> for a long time now. But I'd like to see a few comments as to whether we
>> need a technological mechanism here to enforce the obvious. To me, it
>> just seems totally obvious (any legal comment?) that early C string
>> termination is undermining the intent of the MODULE_LICENSE tag.
>
> I'm not a lawyer, but I can tell you exactly what a lawyer would say:
>
> "well, ya know, it's hard to say when it comes to these issues"
>
> that's the answer to *any* copyright question. :)
to me it even screams "bypassing or a digital copyright enforcement system".
that sounds really close to "D.M.C.A. violation" :)
thank goodness I'm not a laywer...
Auke
next prev parent reply other threads:[~2007-02-01 23:34 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-28 0:41 [PATCH] Blacklist hsfmodem module Alexey Dobriyan
2006-11-01 11:21 ` Jan Engelhardt
2007-02-01 21:20 ` [PATCH] Ban module license tag string termination trick Jan Engelhardt
2007-02-01 21:28 ` [m-i-t part] " Jan Engelhardt
2007-02-01 21:55 ` [PATCH] " Randy Dunlap
2007-02-01 22:17 ` Jon Masters
2007-02-01 22:30 ` Trent Waddington
2007-02-01 23:34 ` Auke Kok [this message]
2007-02-02 8:24 ` David Schwartz
2007-02-02 10:45 ` Helge Hafting
2007-02-03 18:31 ` David Schwartz
2007-02-03 20:47 ` Jan Engelhardt
2007-02-03 22:21 ` Alan
2007-02-03 23:32 ` Jon Masters
2007-02-04 0:05 ` Alan
2007-02-04 7:56 ` David Schwartz
2007-02-07 12:18 ` Helge Hafting
2007-02-07 18:56 ` David Schwartz
2007-02-12 15:50 ` Helge Hafting
2007-02-12 16:42 ` Alan
2007-02-12 22:37 ` David Schwartz
2007-02-02 0:17 ` Tomas Carnecky
2007-02-02 0:51 ` Trent Waddington
2007-02-02 2:19 ` Valdis.Kletnieks
2007-02-02 3:12 ` Arjan van de Ven
2007-02-02 6:15 ` Jon Masters
2007-02-02 14:53 ` Paul Rolland
2007-02-02 15:11 ` Jan Engelhardt
2007-02-02 16:53 ` Randy Dunlap
2007-02-02 17:41 ` Jan Engelhardt
2007-02-02 17:49 ` Randy Dunlap
2007-02-02 19:06 ` Jan Engelhardt
2007-02-03 1:12 ` Randy Dunlap
2007-02-03 1:29 ` Jan Engelhardt
2007-02-02 18:37 ` Paul Rolland
2007-02-02 19:08 ` Jan Engelhardt
2007-02-04 8:14 ` Paul Rolland
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=45C27908.1000202@foo-projects.org \
--to=sofar@foo-projects.org \
--cc=adobriyan@gmail.com \
--cc=akpm@osdl.org \
--cc=jengelh@linux01.gwdg.de \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trent.waddington@gmail.com \
/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.