From owner-freebsd-current Wed Jul 2 22:30:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA20523 for current-outgoing; Wed, 2 Jul 1997 22:30:07 -0700 (PDT) Received: from pluto.plutotech.com (root@[206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA20518 for ; Wed, 2 Jul 1997 22:30:04 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id XAA02164; Wed, 2 Jul 1997 23:28:46 -0600 (MDT) Message-Id: <199707030528.XAA02164@pluto.plutotech.com> To: Nate Williams cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: CVSUP and CVS branches: bug? In-reply-to: Your message of "Wed, 02 Jul 1997 22:45:51 MDT." <199707030445.WAA29217@rocky.mt.sri.com> Date: Wed, 02 Jul 1997 23:28:46 -0600 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >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. There is a 100+ page manual now that is very well written. We've been using Perforce at Pluto since February and I wouldn't even think for a moment about going back to CVS. >Nate > -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================