linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David Schwartz" <davids@webmaster.com>
To: "Larry McVoy" <lm@bitmover.com>, "Richard Stallman" <rms@gnu.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Bitkeeper
Date: Fri, 18 Jul 2003 14:08:32 -0700	[thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKOEIFEHAA.davids@webmaster.com> (raw)
In-Reply-To: <20030718204405.GA658@work.bitmover.com>


> Our license states that you can't use BK if you are developing a similar
> system, i.e., a clone.  Without using BK it's impossible to reverse
> engineer BK to create the clone.  So your message seems to be saying
> "it would be appropriate at this point to violate the BitKeeper license
> in order to write a free client which talks with BitKeeper".

> Larry McVoy              lm at bitmover.com

	My understanding of the relevant case law in the United States is that
these types of restrictions are not allowed under copyright law itself.
They've only been upheld when they're part of a sale contract. You can
certainly argue that a click to an 'I Agree' link constitutes acceptance of
a sale contract. But if someone sits down at a friend's computer that
happens to have BK on it, or finds a copy of BK on a CD someone left at the
lab, you would have a hard time arguing that they agreed to this contract.

	See, for example, ProCD v. Zeidenberg:

"Copyright law forbids duplication, public performance, and so on, unless
the person wishing to copy or perform the work gets permission; silence
means a ban on copying. A copyright is a right against the world. Contracts,
by contrast, generally affect only their parties; strangers may do as they
please, so contracts do not create "exclusive rights." Someone who found a
copy of SelectPhone(TM) on the street would not be affected by the
shrinkwrap license - though the federal copyright laws of their own force
would limit the finder's ability to copy or transmit the application
program."

	IANAL, and in any event, I don't think any court would look fondly on
someone who deliberately contrived a method to claim they're not subject to
the license.

	DS



  parent reply	other threads:[~2003-07-18 20:54 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-18 19:51 Bitkeeper Richard Stallman
2003-07-18 20:06 ` Bitkeeper Rik van Riel
2003-07-18 20:22   ` Bitkeeper nick
2003-07-18 20:40     ` Bitkeeper Shawn
2003-07-18 21:28     ` Bitkeeper Alan Cox
2003-07-19 23:45       ` Bitkeeper Pavel Machek
2003-07-20  0:23         ` Bitkeeper Jeff Garzik
2003-07-18 20:32   ` Bitkeeper Shawn
2003-07-18 20:44     ` Bitkeeper Rik van Riel
2003-07-19 18:42     ` Bitkeeper Jan-Benedict Glaw
2003-07-19 18:49       ` Bitkeeper Larry McVoy
2003-07-19 18:57         ` Bitkeeper Jan-Benedict Glaw
2003-07-19 19:05           ` Bitkeeper Larry McVoy
2003-07-19 20:02             ` Bitkeeper Jan-Benedict Glaw
2003-07-18 20:09 ` Bitkeeper Trever L. Adams
2003-07-18 20:44   ` Bitkeeper Shawn
2003-07-18 21:03   ` Bitkeeper Larry McVoy
2003-07-18 21:58     ` Bitkeeper Trever L. Adams
2003-07-18 22:17   ` Bitkeeper Mike Fedyk
2003-07-18 22:39     ` Bitkeeper Alan Cox
2003-07-19  8:20       ` Bitkeeper Eric W. Biederman
2003-07-19 15:34         ` Bitkeeper Mark Mielke
2003-07-18 22:29   ` Bitkeeper Scott Robert Ladd
2003-07-18 20:30 ` Bitkeeper Michael Buesch
2003-07-18 20:36   ` Bitkeeper Shawn
2003-07-18 20:44 ` Bitkeeper Larry McVoy
2003-07-18 21:03   ` Bitkeeper Shawn
2003-07-18 21:08   ` David Schwartz [this message]
2003-07-18 21:28     ` Bitkeeper Shawn
2003-07-18 21:23   ` Bitkeeper Alan Cox
2003-07-18 21:50     ` Bitkeeper David Lang
2003-07-18 21:54     ` Bitkeeper Valdis.Kletnieks
2003-07-18 22:16       ` Bitkeeper Alan Cox
2003-07-18 22:01     ` Bitkeeper Trever L. Adams
2003-07-18 22:27     ` Bitkeeper Larry McVoy
2003-07-19  9:45       ` Bitkeeper Marcus Metzler
2003-07-19 20:42       ` Bitkeeper Adrian Bunk
2003-07-19 21:57         ` Bitkeeper Larry McVoy
2003-07-19 22:28           ` Bitkeeper Adrian Bunk
2003-07-19 22:39             ` Bitkeeper Larry McVoy
2003-07-19 23:45               ` Bitkeeper Adrian Bunk
2003-07-20  0:02                 ` Bitkeeper Larry McVoy
2003-07-20  0:10                   ` Bitkeeper Tupshin Harper
2003-07-20  0:26                     ` Bitkeeper Valdis.Kletnieks
2003-07-20  1:11                       ` Bitkeeper Jeff Garzik
2003-07-20  0:23                   ` Bitkeeper Jeff Garzik
2003-07-20  0:28                   ` Bitkeeper jiho
2003-07-20  0:30                   ` Bitkeeper Valdis.Kletnieks
2003-07-20  0:50                     ` Bitkeeper Larry McVoy
2003-07-20  0:22                 ` Bitkeeper Jeff Garzik
     [not found]               ` <3F19DA04.80809@c-zone.net>
     [not found]                 ` <20030719235526.GA31428@work.bitmover.com>
2003-07-20  0:21                   ` Bitkeeper jiho
2003-07-19 23:57       ` Bitkeeper Pavel Machek
2003-07-18 21:06 ` Bitkeeper Jörn Engel
2003-07-18 22:00   ` Bitkeeper Svein Ove Aas
2003-07-18 22:25     ` BK is not heaven, sure [Was: Re: Bitkeeper] J.A. Magallon
2003-07-18 23:50 ` Bitkeeper James Simmons
2003-07-19  1:05   ` offtopic crap (was Re: Bitkeeper) David S. Miller
2003-07-19 15:00     ` Jeff Garzik
2003-07-20  2:50 ` Bitkeeper Zack Brown
  -- strict thread matches above, loose matches on Subject: below --
2003-07-19 16:00 Bitkeeper John Bradford
2003-07-19 16:17 ` Bitkeeper Mark Mielke
2003-07-19 10:33 Bitkeeper John Bradford
2003-02-15  8:21 BitKeeper John Bradford
2003-02-15 22:26 ` BitKeeper Pavel Machek
2003-02-16 11:40   ` BitKeeper John Bradford

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=MDEHLPKNGKAHNMBLJOLKOEIFEHAA.davids@webmaster.com \
    --to=davids@webmaster.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=rms@gnu.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;
as well as URLs for NNTP newsgroup(s).