public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Kevin Puetz <puetzk@iastate.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is the BitKeeper network protocol documented?
Date: Fri, 17 Jan 2003 22:39:21 -0800	[thread overview]
Message-ID: <20030118063921.GB23597@work.bitmover.com> (raw)
In-Reply-To: <b0arl3$59p$1@main.gmane.org>

I've sent Jamie mail asking him why he things 3(d) is a problem for him,
we'll see what he says.  If he's working on things that compete with BK 
then the answer is no, if he's not, then there is no problem.

We want to help the kernel team, that should be obvious.  I draw the line
where helping the kernel team hurts BitMover, as would any of you in my
position.  Fortunately, it's pretty rare that anyone talented enough to
work on the kernel also wants to work on source management.

We could change the license to have the standard legalese which says you
can't reverse engineer, etc.  If the community at large would prefer that,
we could discuss it.  I suspect that when you realize the implications of 
that legalese, the BKL will seem a lot nicer by comparison.   Would you
rather have something like:

 You may not yourself and may not permit or enable anyone to:  (i)  modify  or
 translate  the Software; (ii) reverse engineer, decompile, or disassemble the
 Software or otherwise reduce the Software to a form understandable by humans,
 except  to  the extent this restriction is expressly prohibited by applicable
 law notwithstanding this limitation; (iii) rent, lease, loan, resell or  cre-
 ate  derivative  works  based  on  the Software; (iv) merge the Software with
 another product; (v) separate the Software into  its  component  parts;  (vi)
 copy the Software, except (A) as expressly provided herein and (B) as reason-
 ably necessary for back up and recovery purposes; or (vii) remove or  obscure
 any proprietary rights notices, labels, copyrights, trademarks, servicemarks,
 confidentiality notices and/or restricted rights notices on or in  the  Soft-
 ware.

-- 
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm 

  reply	other threads:[~2003-01-18  6:30 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-18  4:33 Is the BitKeeper network protocol documented? Jamie Lokier
2003-01-18  4:57 ` David Schwartz
2003-01-18  5:10   ` Jamie Lokier
2003-01-18  7:23     ` David Schwartz
2003-01-18  7:54       ` [OFFTOPIC] Is the repository of a GPL'd program itself under the GPL? Jamie Lokier
2003-01-20  0:50         ` Richard Stallman
2003-01-18  5:02 ` Is the BitKeeper network protocol documented? Andrew Morton
2003-01-18  5:15   ` Jamie Lokier
2003-01-18  5:29 ` Larry McVoy
2003-01-18  6:11   ` Tupshin Harper
2003-01-18  6:20   ` Kevin Puetz
2003-01-18  6:39     ` Larry McVoy [this message]
2003-01-18  8:09   ` Jamie Lokier
2003-01-18  8:25     ` Andrew Morton
2003-01-18 14:22   ` Roman Zippel
2003-01-19 18:39     ` Andreas Dilger
2003-01-19 18:55       ` Jamie Lokier
2003-01-19 21:50       ` Roman Zippel
2003-01-19 23:26         ` Andreas Dilger
2003-01-19 23:57           ` David Schwartz
2003-01-20  0:20             ` Andreas Dilger
2003-01-20  0:38               ` David Schwartz
2003-01-20 15:52             ` Horst von Brand
2003-01-20 19:43               ` David Schwartz
2003-01-20 19:46               ` David Schwartz
2003-01-21  7:56                 ` Horst von Brand
2003-01-20 14:18           ` Roman Zippel
2003-01-22 12:24   ` Matthias Andree
  -- strict thread matches above, loose matches on Subject: below --
2003-01-18  6:22 Jamie Lokier
     [not found] <20030119235742.AAA13049%shell.webmaster.com@whenever>
2003-01-20  0:36 ` Valdis.Kletnieks
2003-01-20  1:05   ` David Schwartz
2003-01-20 14:28     ` Dana Lacoste
2003-01-20 19:00       ` David Schwartz
2003-01-20 19:31         ` David Lang
2003-01-20 20:19           ` David Schwartz
2003-01-20 20:40             ` John Bradford
2003-01-20 20:48             ` Andreas Dilger
2003-01-20 21:14               ` David Schwartz
2003-01-20 21:58                 ` John Bradford
2003-01-20 21:37               ` Sam Ravnborg
2003-01-20 21:41             ` Rik van Riel
2003-01-21 16:04         ` Dana Lacoste
2003-01-21 18:34           ` David Schwartz
2003-01-21 18:49             ` John Bradford
2003-01-21 18:58             ` Sam Ravnborg
2003-01-21 19:27             ` Dana Lacoste
2003-01-21 21:04               ` David Schwartz
2003-01-21 19:51             ` Hua Zhong
2003-01-22  7:10               ` Jamie Lokier
2003-01-22  7:21                 ` John Alvord
2003-01-22 15:18                 ` Larry McVoy
2003-01-22 15:27                   ` Dana Lacoste
2003-01-22 15:38                     ` Larry McVoy
2003-01-20  1:46   ` David Lang
2003-01-20  1:52   ` Andre Hedrick
     [not found] <20030120010504.AAA18836%shell.webmaster.com@whenever>
2003-01-20  1:37 ` Valdis.Kletnieks
2003-01-20 15:55 Theodore Ts'o
2003-01-20 18:53 ` David Schwartz
     [not found] <20030120194430.AAA20700%shell.webmaster.com@whenever>
2003-01-20 20:32 ` Valdis.Kletnieks
2003-01-20 21:27   ` David Schwartz
2003-01-21  8:51     ` Horst von Brand
2003-01-21  0:28 Cort Dougan
2003-01-21 19:22 Larry McVoy

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=20030118063921.GB23597@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=puetzk@iastate.edu \
    /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