From owner-freebsd-hackers Fri Jun 4 2: 7:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mag.ucsd.edu (mag.ucsd.edu [132.239.34.96]) by hub.freebsd.org (Postfix) with ESMTP id 3CEDA15AF0 for ; Fri, 4 Jun 1999 02:07:03 -0700 (PDT) (envelope-from billh@mag.ucsd.edu) Received: (from billh@localhost) by mag.ucsd.edu (8.8.8/8.8.8) id CAA14437; Fri, 4 Jun 1999 02:02:10 -0700 (PDT) From: Bill Huey Message-Id: <199906040902.CAA14437@mag.ucsd.edu> Subject: Re: 3.2-stable, panic #12 To: wes@softweyr.com (Wes Peters) Date: Fri, 4 Jun 1999 02:02:10 -0700 (PDT) Cc: billh@mag.ucsd.edu (Bill Huey), freebsd-hackers@freebsd.org In-Reply-To: <375768A3.C556E77C@softweyr.com> from "Wes Peters" at Jun 3, 99 11:48:19 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've been following this conversation with growing concern. It seems > to me there is a fairly simple solution to this problem: create a > branch for the ongoing VM work, enable commit privs on the branch for > Matt and anyone else who's going to join in the fun, and then at times > when they think it is appropriate and things have been adequately > reviewed, we have a little merge-mania and things are better than ever. > > Are there any technological boundaries that prevent us from doing this? > This is how we do it in the paid-for-code world. ;^) It's been rumored that CVS itself is the technical factor limiting one's ability to fork the tree because of the nature of how CVS update files by clobbering them. I had a talk to someone the the #freebsd IRC channel about this. The name slips my mind right now. bill > Wes Peters Softweyr LLC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message