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

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 

  reply	other threads:[~2002-03-07  5:32 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 [this message]
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

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=20020306213238.D3240@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