Date: Fri, 4 Jun 1999 02:02:10 -0700 (PDT) From: Bill Huey <billh@mag.ucsd.edu> To: wes@softweyr.com (Wes Peters) Cc: billh@mag.ucsd.edu (Bill Huey), freebsd-hackers@freebsd.org Subject: Re: 3.2-stable, panic #12 Message-ID: <199906040902.CAA14437@mag.ucsd.edu> In-Reply-To: <375768A3.C556E77C@softweyr.com> from "Wes Peters" at Jun 3, 99 11:48:19 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199906040902.CAA14437>