public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Pollei <stephen_pollei@comcast.net>
To: davids@webmaster.com
Cc: "Jp@Enix. Org" <jp@enix.org>, linux-kernel@vger.kernel.org
Subject: RE: Possible GPL infringement in Broadcom-based routers
Date: 06 Nov 2004 13:40:37 -0800	[thread overview]
Message-ID: <1099777244.970.60.camel@fury> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKGEIEPJAA.davids@webmaster.com>

[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]

On Sat, 2004-11-06 at 12:09, David Schwartz wrote:
> 	.... But since I refused the GPL, why does it matter
> what the GPL says?!
> 
It matters, because in a dispute the copyright holder(s) will file a
civil case alleging copyright violation(s) on your part. When you
receive this, you will have no defense to this charge unless you claim
that you received a license from the copyright holder(s). The copyright
holder(s) will at that point ask "What license would that be?". You will
answer "the GPL of course!" .

After you have acknowledged the GPL as part of your defense --  Then and
only then would the debate move to whether or not you are within the
four corners of the license. However if you don't acknowledge the GPL
then you are making a summary judgment against you quite likely -- as
the court will find it as a fact not in material dispute that you had no
permission to do anything with the copyrighted work(s) at all.

So I guess you are completely right; if you refuse to use the GPL as a
defense, then it doesn't matter what it does or doesn't say -- you're
going to fry by default.

-- 
http://dmoz.org/profiles/pollei.html
http://sourceforge.net/users/stephen_pollei/
http://www.orkut.com/Profile.aspx?uid=2455954990164098214
http://stephen_pollei.home.comcast.net/
GPG Key fingerprint = EF6F 1486 EC27 B5E7 E6E1  3C01 910F 6BB5 4A7D 9677

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-11-06 21:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-05 18:43 Possible GPL infringement in Broadcom-based routers Adam J. Richter
2004-11-05 19:59 ` David Schwartz
2004-11-06  3:23   ` David Woodhouse
2004-11-06 20:09     ` David Schwartz
2004-11-06 21:40       ` Stephen Pollei [this message]
2004-11-07 17:05       ` David Woodhouse
2004-11-06 13:38 ` Horst von Brand
2004-11-06 15:49   ` Arjan van de Ven
2004-11-07 21:08     ` Ryan Anderson
  -- strict thread matches above, loose matches on Subject: below --
2004-11-06 10:40 Adam J. Richter
2004-11-05 18:51 ` Michael Poole
2004-11-05 18:58 ` Disconnect
2004-11-05 19:03 ` David Schwartz
2004-11-05 19:38   ` linux-os
2004-11-05 19:06 ` Horst von Brand
2004-11-05 19:39   ` Arjan van de Ven
2004-11-06  3:21   ` Kyle Moffett
2004-11-05 18:31 Adam J. Richter
2004-11-05 18:20 Adam J. Richter
2004-11-05 20:00 ` Michael Poole
2004-11-04 23:33 Jérôme Petazzoni
2004-11-04 23:57 ` David Schwartz
2004-11-05  0:23   ` Kyle Moffett
2004-11-05 15:27   ` David Woodhouse
2004-11-05  4:05 ` Scott Lockwood
2004-11-05 20:28 ` Tonnerre

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=1099777244.970.60.camel@fury \
    --to=stephen_pollei@comcast.net \
    --cc=davids@webmaster.com \
    --cc=jp@enix.org \
    --cc=linux-kernel@vger.kernel.org \
    /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