public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Steinmetz <ast@domdv.de>
To: Dave Jones <davej@redhat.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	typo@shaw.ca,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Paulo Marques <pmarques@grupopie.com>
Subject: Re: Linuxant/Conexant HSF/HCF Modem Drivers Unlocked
Date: Fri, 29 Oct 2004 22:37:26 +0200	[thread overview]
Message-ID: <4182AA06.5030901@domdv.de> (raw)
In-Reply-To: <20041029200011.GA18508@redhat.com>

Dave Jones wrote:
> On Fri, Oct 29, 2004 at 02:50:42PM +0100, Alan Cox wrote:
>  > On Gwe, 2004-10-29 at 13:43, Chad Christopher Giffin wrote:
>  > > I still find myself deeply troubled and questioning the legalities of
>  > > using "GPL\0[...]" in the license string of a non-GPL module.  As it is
>  > > a blatant lie.  
>  > 
>  > Oh its almost certainly a criminal offence in the USA - the DMCA for
>  > example. The \0 stupidity checker needs to go into the kernel.
> 
> Copy protection arms-races are always fun. If we did this, no doubt
> some enterprising individual would find that some other value
> also has the same effect.  You need to throw out anything else
> thats non alphanumeric too.  (plus '/' for 'Dual BSD/GPL' and friends)
> 

How about 'GPL\rMy real license'? Which means: yes, you're absolutely right.
-- 
Andreas Steinmetz                       SPAMmers use robotrap@domdv.de

  parent reply	other threads:[~2004-10-29 22:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-29  6:52 Linuxant/Conexant HSF/HCF Modem Drivers Unlocked Chad Christopher Giffin
2004-10-29 11:18 ` Paulo Marques
2004-10-29 12:43   ` Chad Christopher Giffin
2004-10-29 12:49     ` Arjan van de Ven
2004-10-29 13:50     ` Alan Cox
2004-10-29 20:00       ` Dave Jones
2004-10-29 20:21         ` Willy Tarreau
2004-10-29 20:37         ` Andreas Steinmetz [this message]
2004-10-29 22:46           ` Kenneth Aafløy
2004-10-29 22:54             ` Andreas Steinmetz

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=4182AA06.5030901@domdv.de \
    --to=ast@domdv.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmarques@grupopie.com \
    --cc=typo@shaw.ca \
    /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