From owner-freebsd-current Wed Jul 2 21:46:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA18625 for current-outgoing; Wed, 2 Jul 1997 21:46:00 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA18620 for ; Wed, 2 Jul 1997 21:45:58 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id WAA29217; Wed, 2 Jul 1997 22:45:51 -0600 (MDT) Date: Wed, 2 Jul 1997 22:45:51 -0600 (MDT) Message-Id: <199707030445.WAA29217@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: current@freebsd.org Subject: Re: CVSUP and CVS branches: bug? In-Reply-To: <17252.867895713@time.cdrom.com> References: <199707030014.RAA29620@bubba.whistle.com> <17252.867895713@time.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard writes: > > Half-serious suggestion... why not ask Perforce if they would like > > to "donate" their source management system for FreeBSD's non-commercial > > use? Not likely, but anyway here's a ref to it: > > They've already offered us the server for $1 on freefall and an > unlimited number of clients, for whomever wants to use the repository > maintained there. Any other group using FreeBSD non-profit also gets > the same $1/server deal, so they can run their own repositories. > Our CVSmeister personally likes perforce. > > Truly, the barriers here are not technical or financial, they're > political. :-) I disagree. There are many 'technical' features that CVS gives us that aren't available in Perforce, or are done in a much different fashion. That, and the documentation is pretty non-existant. When I reviewed/evaluated Perforce for work, the lack of decent documentation was my final sticking point, and even the developers agreed that it needed work. (Though, they were real good about providing specific answers to specific questions I had regarding the product, but that doesn't work well with a bunch of developers who are fairly naive when it comes to SCM's). That was last Fall, so things may have changed since then. Nate