From owner-freebsd-current Fri Jun 23 4:16: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 5584537B7C5 for ; Fri, 23 Jun 2000 04:16:06 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial-195-14-250-90.netcologne.de [195.14.250.90]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id NAA06676; Fri, 23 Jun 2000 13:15:46 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id NAA05779; Fri, 23 Jun 2000 13:14:48 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Fri, 23 Jun 2000 13:14:48 +0200 (CEST) Message-Id: <200006231114.NAA05779@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: sos@freebsd.dk Cc: current@FreeBSD.ORG In-reply-to: <200006211934.VAA31186@freebsd.dk> (message from Soren Schmidt on Wed, 21 Jun 2000 21:34:51 +0200 (CEST)) Subject: Re: HEADS UP: Destabilization due to SMP development Reply-To: van.woerkom@netcologne.de References: <200006211934.VAA31186@freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Using a non opensource commercial version control system is just > to ask for bad carma, extended murphy fields and whatnot in an > opensource volounteer project... I would like to understand the discussed weakness of cvs regarding branches. Could someone explain it (in private) or point me to a link? I ask because I had to work a lot with MKS SI (RCS based) and it was OK to manage different branches with it. So I assumed cvs as a kind of successor to rcs is able to do this too. Or do people just like an improved architecture? I understand that systems like Perforce are handling diffs to the code base not file orientated but rather goal orientated which might give a much better overview. Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message