public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Pavel Machek <pavel@suse.cz>,
	Florian Weimer <Weimer@CERT.Uni-Stuttgart.DE>,
	linux-kernel@vger.kernel.org
Subject: Re: [OFF TOPIC] BK license change
Date: Mon, 29 Apr 2002 12:45:14 -0700	[thread overview]
Message-ID: <20020429124514.O15730@work.bitmover.com> (raw)
In-Reply-To: <20020426042242.A294@toy.ucw.cz> <Pine.LNX.4.44L.0204291633010.1960-100000@imladris.surriel.com>

FYI - You won't see me replying to this because he's joined some others in
my procmail filter, enabling me to get more work done.  I love procmail.

Besides, Rik is doing a great job, thanks Rik!  

To underscore Rik's point: it took 4 years of at least 6 day/week efforts
by a team that varied in size from 3-8 engineers to get BitKeeper where
it is today.  Pavel is welcome to try and do better, but he sure as
hell isn't going to do it in his spare time.  Nobody is, it's a much
harder problem than it looks like.  I really wish people would try it
and find out.  Maybe I'm wrong, in which case we can all get on to doing
something more fun.

On Mon, Apr 29, 2002 at 04:34:30PM -0300, Rik van Riel wrote:
> On Fri, 26 Apr 2002, Pavel Machek wrote:
> > > In short: go build a better answer, and until you do it, how about
> > > easing off on the "BK is evil corporate software" mantra a bit?  It's
> >
> > BK *is* evil corporate software, with unique trapdoor capabilities, and
> > with unique ability to take away rights from user any time it wants.
> 
> BK is made available to us at no cost;  BK is saving Linus and
> Marcelo a lot of work, making it possible for them to merge more
> patches into the kernel.
> 
> If you only spent 10% of the energy you spent complaining on
> making a bitkeeper replacement, maybe you'd realise that Larry
> is making a very useful contribution.
> 
> regards,
> 
> Rik
> -- 
> Bravely reimplemented by the knights who say "NIH".
> 
> http://www.surriel.com/		http://distro.conectiva.com/

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

  reply	other threads:[~2002-04-29 19:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-21 16:57 [OFF TOPIC] BK license change Larry McVoy
2002-04-21 12:12 ` Daniel Phillips
2002-04-21 16:29 ` Greg KH
2002-04-22  7:33 ` Simon Fowler
2002-04-22 21:35 ` Larry McVoy
2002-04-21 22:14   ` Daniel Phillips
2002-04-22 22:29     ` Andreas Dilger
2002-04-21 22:52       ` Daniel Phillips
2002-04-22 23:12         ` Doug Ledford
2002-04-21 23:34           ` Daniel Phillips
2002-04-22 22:22   ` Jeff Garzik
2002-04-22 22:52     ` Larry McVoy
2002-04-25 15:01   ` Pavel Machek
2002-04-27  9:30     ` Florian Weimer
2002-04-27 13:45       ` Mr. James W. Laferriere
2002-04-27 20:34       ` Larry McVoy
2002-04-26  4:22         ` Pavel Machek
2002-04-29 19:34           ` Rik van Riel
2002-04-29 19:45             ` Larry McVoy [this message]
2002-04-30  5:36               ` Pavel Janík
  -- strict thread matches above, loose matches on Subject: below --
2002-04-27 18:13 Christoph Lameter
2002-04-27 18:25 ` Russell King
2002-04-27 18:30 ` Alexander Viro
2002-04-27 21:50   ` Martin Dalecki
2002-04-28 16:55     ` Richard Gooch

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=20020429124514.O15730@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=Weimer@CERT.Uni-Stuttgart.DE \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=riel@conectiva.com.br \
    /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