public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Tom Lord <lord@regexps.com>
Cc: linux-kernel@vger.kernel.org, lm@bitmover.com, hozer@drgw.net,
	davej@suse.de
Subject: Re: Why not an arch mirror for the kernel?
Date: Thu, 7 Mar 2002 08:00:13 -0800	[thread overview]
Message-ID: <20020307080013.B26028@work.bitmover.com> (raw)
In-Reply-To: <200203071425.GAA06679@morrowfield.home> <20020306190419.E31751@work.bitmover.com> <20020306225652.Q1682@altus.drgw.net> <20020306213238.D3240@work.bitmover.com> <200203072147.NAA08182@morrowfield.home>
In-Reply-To: <200203072147.NAA08182@morrowfield.home>; from lord@regexps.com on Thu, Mar 07, 2002 at 01:47:07PM -0800

On Thu, Mar 07, 2002 at 01:47:07PM -0800, Tom Lord wrote:
> 	More than a year ago, we had some research done to see what it
> 	would cost to reproduce BitKeeper from scratch. At that point,
> 	it was estimated to be about $12,000,000 and at least 3.5
> 	years from the time a good team started.
> 
> That sounds to me like the kind of research you'd want to include in a
> proposal to potential investors: to prove that you have a unique
> strength in the market being addressed (a "barrier to entry").  I find
> the apparent urgency and hysteria with which you defame arch on this
> list to be pretty funny.

Hmm, maybe I am urgent, I'm packing for a long weekend.  Anyway, you're
missing my points, and I don't see why, it's in your best interest to
get it.  Let's try it as a question, and see if that works.  

Suppose all the kernel people started using your tool today.  On your
web page, you have a long list of things which need to be done to Arch
and your best case scenario is that it will take about year to do them
(your words, not mine).  So suppose the kernel people start using
your tool right now, bury you in requests for changes, and you can't
keep up.  They leave because it doesn't work.  End result: big negative
endorsement from the kernel team.  Obviously, you don't want that, and
equally obviously, you understand the probability of that (read your
own website), so maybe with all that, you'll understand why I said that
if you want to succeed you should pick a small group and work with them
closely until Arch is ready.

OK, let's address your other point.  It sounds like you think we're trying
to convince VC's of something and somehow doing so means that I need to
be badmouthing Arch.  Or maybe you think we have VC's leaning on us and
they are telling us that we'd better kill Arch.  Or some such thing, the
implication being that investors (or lack of them, or desire for them)
are causing me to go after Arch.  That's not true, we are not now and
were not then in discussions with VC's, the only investment BitMover 
has is from engineers who work here on the code.  We're self supporting
through sales of the product and we are not dependent on or subject to
the whims of any VC.  And we've declined offers to be bought so we could
stay that way.  Go read the ArsDigita archives and you will understand
why.
-- 
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm 

      reply	other threads:[~2002-03-07 16:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-07 14:25 Why not an arch mirror for the kernel? Tom Lord
2002-03-07  3:04 ` Larry McVoy
2002-03-07  4:56   ` Troy Benjegerdes
2002-03-07  5:32     ` Larry McVoy
2002-03-07 10:09       ` Jan Harkes
2002-03-07 16:15         ` Larry McVoy
2002-03-07 16:02       ` Troy Benjegerdes
2002-03-07 17:12       ` Henning P. Schmiedehausen
2002-03-07 21:47       ` Tom Lord
2002-03-07 16:00         ` Larry McVoy [this message]

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=20020307080013.B26028@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=davej@suse.de \
    --cc=hozer@drgw.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lord@regexps.com \
    /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