mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Hazelton <dhazelton@enter.net>
To: Valdis.Kletnieks@vt.edu
Cc: davids@webmaster.com, espie@nerim.net, linux-kernel@vger.kernel.org
Subject: Re: GPL weasels and the atheros stink
Date: Tue, 4 Sep 2007 13:20:27 -0400	[thread overview]
Message-ID: <200709041320.27610.dhazelton@enter.net> (raw)
In-Reply-To: <31129.1188918652@turing-police.cc.vt.edu>

On Tuesday 04 September 2007 11:10:52 Valdis.Kletnieks@vt.edu wrote:
> On Mon, 03 Sep 2007 17:23:37 PDT, David Schwartz said:
> > > Wrong - I said "You can't complain about Person A doing X when
> > > you let Person
> > > B do X without complaint".
> >
> > Yes, I can. There is no inconsistency between acting in one case and
> > failing to act in another. We need not act in every possible case where
> > we could act to preserve our right to act in a particular case.
>
> You *do* however need to be aware that in some cases, public inactivity
> and/or statements that something will not be acted on may estoppel any
> future attempts to enforce something.

Exactly. However, inactivity can be construed as lack of knowledge that 
something is occurring. (ie: the RIAA didn't start acting on file-sharing 
until they became aware of Napster)

But for said estoppel to not be a factor you will have to prosecute and/or 
file suit on all instances of the activity. (And filing a suit and then 
dropping it against some of the people that you filed suit against - ie: you 
file suit against persons A and B and then drop the suit against person A in 
its entirety - because you only wanted to prosecute person B for the action, 
you are leaving yourself open to lawsuits on a number of counts.)

DRH

-- 
Dialup is like pissing through a pipette. Slow and excruciatingly painful.

  reply	other threads:[~2007-09-04 17:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-02 14:03 Marc Espie
2007-09-02 16:52 ` Kyle Moffett
2007-09-02 16:54 ` Alan Cox
2007-09-02 17:16 ` Oleg Verych
2007-09-02 17:34 ` Michael Tharp
2007-09-02 17:41 ` Jeff Garzik
2007-09-02 17:57 ` Jeff Garzik
2007-09-02 20:22 ` Bernd Petrovitsch
2007-09-03  2:01 ` David Schwartz
2007-09-03  2:57   ` Daniel Hazelton
2007-09-03  9:47     ` David Schwartz
2007-09-03 17:43       ` Daniel Hazelton
2007-09-04  0:23         ` David Schwartz
2007-09-04  0:49           ` Daniel Hazelton
2007-09-04 15:10           ` Valdis.Kletnieks
2007-09-04 17:20             ` Daniel Hazelton [this message]
2007-09-03 17:18     ` Krzysztof Halasa
2007-09-03 18:11       ` Daniel Hazelton
2007-09-03 16:12 ` Valdis.Kletnieks
2007-09-04 15:01   ` Jarek Poplawski

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=200709041320.27610.dhazelton@enter.net \
    --to=dhazelton@enter.net \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=davids@webmaster.com \
    --cc=espie@nerim.net \
    --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

Powered by JetHome