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


I have the sense that you (lm) are trying to draw me into a flame war
on an inappropriate mailing list.  I'm not interested.

I agree with this:

	lm:
	Go use arch and find out if you really want it.
	[http://www.regexps.com/#arch -- the artwork (which is not
	 mine) is worth the price of admission.]

But caution early adopters to read this:
	
	http://www.lib.uaa.alaska.edu/linux-kernel/archive/2002-Week-09/0856.html


For humor, let me add the juxtaposition of this:

	lm:
	Arch has one guy with no money and a pile of shell scripts.

with this:

	lm:
	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.

-t



   Date: Wed, 6 Mar 2002 21:32:38 -0800
   From: Larry McVoy <lm@bitmover.com>
   Cc: Tom Lord <lord@regexps.com>, linux-kernel@vger.kernel.org, davej@suse.de
   Mail-Followup-To: Larry McVoy <lm@work.bitmover.com>,
	   Troy Benjegerdes <hozer@drgw.net>, Tom Lord <lord@regexps.com>,
	   linux-kernel@vger.kernel.org, davej@suse.de
   Content-Type: text/plain; charset=us-ascii
   Content-Disposition: inline
   User-Agent: Mutt/1.2.5.1i
   X-UIDL: 3e59c456006ecac71f192a6a0da64314

   On Wed, Mar 06, 2002 at 10:56:52PM -0600, Troy Benjegerdes wrote:
   > > > I am working on some tools that will help to implement automatic,
   > > > incremental, bidirectional gateways between arch, Subversion, and Bk.
   > > 
   > > Gateways, yes, bidirectional, no.  Arch doesn't begin to maintain
   > > the metadata which BK maintains, so it can't begin to solve the
   > > same problems.  If you have a bidirectional gateway, you reduce BK
   > > to the level of arch or subversion, in which case, why use BK at all?
   > > If CVS/Arch/Subversion/whatever works for you, I'd say just use it and
   > > leave BK out of it.
   > 
   > Okay Larry, reality check here... 

   Go use arch and find out if you really want it.  Using arch at this
   point is about as smart as using BK 3 years ago.  Cort did it 2 years ago
   and that was painful enough.  To foist arch at this point on people is
   actually the fastest way to kill it as a project.  These tools take time
   to mature and if you want to help arch be prepared to do the same amount
   of work that Cort did with BK.  It was a lot of work and time on his part.

   And why Arch and not subversion?  Subversion has more people working on
   it, Collab has put a pile of money into it, it has the Apache guy working
   on it, and Arch has one guy with no money and a pile of shell scripts.
   Come on.  There is nothing free in this life, if one guy and some hacking
   could solve this problem, it would have been solved long ago.

   I don't like gateways because they force everyone down to whatever
   is the highest level of functionality that the weakest system can do.
   It's exactly like a stereo system.  You don't spend $4000 on really nice
   system and then try and drive it with $5 of speaker wire.  It will suck,
   it's as good as the weakest part.  In spite of your claims to the contrary,
   Troy, it is really not in our best interests to make a BK<->$OTHER_SCM
   gateway if that means that BK now works only as well as those other
   SCM systems.  That's just stupid.  If you want to do that, you do it,
   but don't foist the work off on me by trying to pretend it's good for BK,
   it's not.  Diluting BK down to the level of average SCM is completely
   pointless and a waste of time.
   -- 
   ---
   Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm 



  parent reply	other threads:[~2002-03-07  9:47 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 [this message]
2002-03-07 16:00         ` 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=200203072147.NAA08182@morrowfield.home \
    --to=lord@regexps.com \
    --cc=davej@suse.de \
    --cc=hozer@drgw.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.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