From: Troy Benjegerdes <hozer@drgw.net>
To: Larry McVoy <lm@work.bitmover.com>, Tom Lord <lord@regexps.com>,
linux-kernel@vger.kernel.org, davej@suse.de
Subject: Re: Why not an arch mirror for the kernel?
Date: Thu, 7 Mar 2002 10:02:39 -0600 [thread overview]
Message-ID: <20020307100239.R1682@altus.drgw.net> (raw)
In-Reply-To: <200203071425.GAA06679@morrowfield.home> <20020306190419.E31751@work.bitmover.com> <20020306225652.Q1682@altus.drgw.net> <20020306213238.D3240@work.bitmover.com>
In-Reply-To: <20020306213238.D3240@work.bitmover.com>; from lm@bitmover.com on Wed, Mar 06, 2002 at 09:32:38PM -0800
> 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 didn't include subversion because no one has volunteered help make
gateway stuff from the subversion project. Let's concentrate one gateway
setup first.
> 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.
It is not my intention to force any kind of a 'lowest common denominator'
setup. Going from a system with fewer capabilities to one with greater
capabilities (i.e., currently arch->bk) is going to require some manual
intervention from $MAINTAINER.
What I'd like to see is someone volunteer to help develop gateway scripts
(where did all those patchbot people go now?). Then I'd like to see
someone volunteer to be a maintainer to run a gateway so that people that
feel arch is a better solution can use it, and those that feel BK is a
better solution can get on with life and not leave anyone out because they
may have issues with the bk license, or even real technical issues with
BK.
Obviously using arch is going to be harder, because it is nowwhere near
mature as BK is. Some people are willing to make that tradeoff.
--
Troy Benjegerdes | master of mispeeling | 'da hozer' | hozer@drgw.net
-----"If this message isn't misspelled, I didn't write it" -- Me -----
"Why do musicians compose symphonies and poets write poems? They do it
because life wouldn't have any meaning for them if they didn't. That's
why I draw cartoons. It's my life." -- Charles Schulz
next prev parent reply other threads:[~2002-03-07 16:03 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 [this message]
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=20020307100239.R1682@altus.drgw.net \
--to=hozer@drgw.net \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@work.bitmover.com \
--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