Date: Wed, 18 Aug 2004 11:42:52 -0400 (EDT) From: Robert Watson <rwatson@freebsd.org> To: Thomas Dickey <dickey@radix.net> Cc: current@freebsd.org Subject: Re: Public Access to Perforce? Message-ID: <Pine.NEB.3.96L.1040818114128.55952D-100000@fledge.watson.org> In-Reply-To: <20040818140525.GA5546@saltmine.radix.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 18 Aug 2004, Thomas Dickey wrote: > On Wed, Aug 18, 2004 at 05:57:19PM +0400, Roman Kurakin wrote: > > I fully agree with you. But this not affect "open source"ness. > > I'd rather call it open development. > > If the change history(*) is locked up in a form that doesn't provide > ready access, there's no distinction. > > (*) noting of course that for many projects the change history comments > are worthless. You'll notice that developers using Perforce are careful to include complete change desriptions when changes are merged to CVS. Often, better ones, because the changes are complete. It's not necessary to commit every mistake to CVS, which is a large part of what Perforce allows us to avoid. This is intentional: FreeBSD developers consider CVS to be the "real" repository, and Perforce to be a working area in which to explore ideas before merging to CVS. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1040818114128.55952D-100000>