From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Josh Boyer <jdub@us.ibm.com>
Cc: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
Alessandro Sappia <a.sappia@ngi.it>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: GPL Violation of Linux in Telsey Video Station Product
Date: Mon, 04 Oct 2004 13:09:06 +0100 [thread overview]
Message-ID: <1096891745.18875.0.camel@localhost.localdomain> (raw)
In-Reply-To: <1096894500.22034.15.camel@weaponx.rchland.ibm.com>
> I'm all for the GPL and making sure it's followed, but could we move
> such discussions some place else? This is supposed to be a development
> list. Maybe creating a linux-gpl list (or whatever) would be better?
See www.gpl-violations.org
next prev parent reply other threads:[~2004-10-04 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 12:16 GPL Violation of Linux in Telsey Video Station Product Alessandro Sappia
2004-10-04 13:44 ` Denis Vlasenko
2004-10-04 12:55 ` Josh Boyer
2004-10-04 12:09 ` Alan Cox [this message]
2004-10-04 16:17 ` Micha Feigin
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=1096891745.18875.0.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=a.sappia@ngi.it \
--cc=jdub@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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