From owner-freebsd-current Wed Jun 21 12:35:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 46F5C37B951 for ; Wed, 21 Jun 2000 12:35:16 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA31186; Wed, 21 Jun 2000 21:34:51 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200006211934.VAA31186@freebsd.dk> Subject: Re: HEADS UP: Destabilization due to SMP development In-Reply-To: <200006211856.MAA82369@harmony.village.org> from Warner Losh at "Jun 21, 2000 12:56:00 pm" To: imp@village.org (Warner Losh) Date: Wed, 21 Jun 2000 21:34:51 +0200 (CEST) Cc: jkh@zippy.osd.bsdi.com (Jordan K. Hubbard), bwithrow@nortelnetworks.com (Robert Withrow), phk@critter.freebsd.dk (Poul-Henning Kamp), brian@Awfulhak.org (Brian Somers), dillon@apollo.backplane.com (Matthew Dillon), jasone@canonware.com (Jason Evans), current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Warner Losh wrote: > In message <12213.961613148@localhost> "Jordan K. Hubbard" writes: > : Everyone talks about using bitkeeper but none of the people who > : recommend it have ever actually tried to use it for anything. > : Before such recommendations will bear weight, this needs to > : change. :) > > In that case, I'd recommend perforce :-) I used it extensively at > Pluto while I was there. I'd love to see FreeBSD use it. The > non-open source ness of it is a bummer, but how much pain are we > willing to tolerate for our ideals? :-) Alot. 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... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message