public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Henning P. Schmiedehausen" <hps@intermeta.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Why not an arch mirror for the kernel?
Date: Thu, 7 Mar 2002 17:12:12 +0000 (UTC)	[thread overview]
Message-ID: <a6871c$151$1@forge.intermeta.de> (raw)
In-Reply-To: <200203071425.GAA06679@morrowfield.home> <20020306190419.E31751@work.bitmover.com> <20020306225652.Q1682@altus.drgw.net> <20020306213238.D3240@work.bitmover.com>

Larry McVoy <lm@bitmover.com> writes:

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

One of the most important reasons why packages like CVS, RCS (and SCCS
and I do intend the pun. ;-) ) don't die is C-x C-q and the vc package.

The fact that bk is SCCS compatible here is IMHO one of the really big
positive points.

	Regards
		Henning


-- 
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen       -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH     hps@intermeta.de

Am Schwabachgrund 22  Fon.: 09131 / 50654-0   info@intermeta.de
D-91054 Buckenhof     Fax.: 09131 / 50654-20   

  parent reply	other threads:[~2002-03-07 17:12 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 [this message]
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='a6871c$151$1@forge.intermeta.de' \
    --to=hps@intermeta.de \
    --cc=linux-kernel@vger.kernel.org \
    /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