From owner-freebsd-current Thu Feb 21 20:40:47 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by hub.freebsd.org (Postfix) with ESMTP id CD03C37B416 for ; Thu, 21 Feb 2002 20:40:43 -0800 (PST) Received: (qmail 12758 invoked from network); 22 Feb 2002 04:40:31 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.91.136.163]) (envelope-sender ) by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 22 Feb 2002 04:40:31 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 21 Feb 2002 23:39:40 -0500 (EST) From: John Baldwin To: Robert Watson Subject: Re: Patch to improve mutex collision performance Cc: current@FreeBSD.ORG, "David O'Brien" , Jake Burkholder , Greg Lehey , Matthew Dillon , Dag-Erling Smorgrav Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 21-Feb-02 Robert Watson wrote: > > On 21 Feb 2002, Dag-Erling Smorgrav wrote: > >> Matthew Dillon writes: >> > I'm not interested in using P4. I think it's a mistake. That is, I >> > think it is being severely overused. [...] >> >> Frankly, although I use Perforce myself for PAM work, I agree with Matt >> here. Most of what is going on in the Perforce should be happening on >> branches in our main repo, if only CVS didn't suck so bad at branching. >> >> I would like to suggest that we consider transitioning our main repo to >> Subversion. It's reasonably similar to cvs, and has all the features we >> need that cvs lack: metadata versioning, atomic commits, cheap >> branching... > > The problem is CVS. The solution is unclear. In the mean time, people > are using Perforce because it's an effective tool to do the job. Believe > me, I'd rather *not* be using two (or two and a half) different version > control and software source management schemes, but the practical reality > is that CVS cannot provide what I need to do what I do. Once there's a > reliable free version control system that can be the One True System, I'll > be extremely pleased to use it. Until then, well... :-) Yep, if subversion ends up being a p4 + decent diffs + annotate + repository replication (p4's vcp looks uber leet) + offline mode, then I'm all for it. :) It would be much easier to not be having to use p4 for work branches since I and others could just reverse integrate our changes into HEAD from the side branches. As it is, we have to create diffs and then patch them into CVS. This is part of the reason I think that p4 doesn't have the greatest diffs btw: you don't need diffs to move code from a work branch into HEAD, you can just reverse integ and it DTRT for you. Plus, if others want to see what you are up to, they can just check out your branch rather than having to pass diffs around. Basically, I don't think p4 was designed for people passing diffs around, folks are supposed to instead be looking at each others branches. However, that's not the way FreeBSD works atm (esp. since CVS is our real SCM), so we end up using p4 in possibly one of the worst ways possible. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message