From owner-freebsd-current Mon Feb 24 18:36:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA11625 for current-outgoing; Mon, 24 Feb 1997 18:36:38 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA11619 for ; Mon, 24 Feb 1997 18:36:35 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id TAA19435; Mon, 24 Feb 1997 19:36:27 -0700 (MST) Date: Mon, 24 Feb 1997 19:36:27 -0700 (MST) Message-Id: <199702250236.TAA19435@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Jimbo Bahooli Cc: freebsd-current@freebsd.org Subject: Re: anoncvs server In-Reply-To: References: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Is an anoncvs being worked on, or planned to be added soon? I *certainly* don't speak for core, but anoncvs is a *huge* networking/CPU load, much more than CVSup and the CPU load is *much* higher than SUP (though the network load can be better than SUP). > In my brief OpenBSD use the anoncvs setup really made it easy to get > all the source code and do local changes. CVSup is really the solution for people who want to do local changes. Granted, the CVS tree is pretty large, but since disk space is fairly cheap (except on laptops ;( ), people doing local development should get the CVS tree. Note that you don't have to get *everything*, simply the base stuff plus whatever parts of the tree you are working on. You may also need to get the 'contrib' tree, since the addition of it broke the nice separation of each part of the tree from one-another. Nate