From owner-freebsd-current Tue May 4 0: 4: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A844614E8A for ; Tue, 4 May 1999 00:03:59 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA08612; Tue, 4 May 1999 01:03:17 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA55538; Tue, 4 May 1999 01:04:35 -0600 (MDT) Message-Id: <199905040704.BAA55538@harmony.village.org> To: Ollivier Robert Subject: Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files) Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sun, 02 May 1999 01:52:16 +0200." <19990502015216.A915@keltia.freenix.fr> References: <19990502015216.A915@keltia.freenix.fr> Date: Tue, 04 May 1999 01:04:35 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990502015216.A915@keltia.freenix.fr> Ollivier Robert writes: : WHat are the improvements compared to Perforce ? After working with Perforce for 9 month at Pluto, I'd have to say it is head and shoulders above CVS. It is a different style of source management, where you have to explicitly open things, but its ability to deal with branches has made it possible to have an extensive set of changes from FreeBSD for pluto boxes and still stay sane. And deal with multiple branches, and deal well with merging. CVSup is still faster at updates that perforce, however... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message