Date: Wed, 18 Aug 2004 14:42:07 -0700 From: Julian Elischer <julian@elischer.org> To: drhodus@machdep.com Cc: current@freebsd.org Subject: Re: Public Access to Perforce? Message-ID: <4123CD2F.7060901@elischer.org> In-Reply-To: <fe77c96b04081807482775809d@mail.gmail.com> References: <Pine.NEB.3.96L.1040818090519.36428F-100000@fledge.watson.org> <fe77c96b04081807482775809d@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
David Rhodus wrote: > On Wed, 18 Aug 2004 09:22:36 -0400 (EDT), Robert Watson > <rwatson@freebsd.org> wrote: > >>On Tue, 17 Aug 2004, David Rhodus wrote: >> >> > > The trustedbsd trees are the only thing exported there, well for other > than some mostly dead trees. None of the TLS, AMD64, NETSMP, and who > knows what else since its not redly a public forum. Actually the TLS IS exported ..It's in the KSE branch which is exported. > > >>I think you'd have to work fairly hard to find open source projects that >>have no ouststanding local patch sets of as-yet uncommitted and > > > So with perforce development software, fbsd will become extra stable > hence removing the need for the -current tree ? > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4123CD2F.7060901>