From owner-freebsd-current@FreeBSD.ORG Wed Aug 18 12:50:09 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B187E16A4CE for ; Wed, 18 Aug 2004 12:50:09 +0000 (GMT) Received: from hanoi.cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E46C43D1D for ; Wed, 18 Aug 2004 12:50:08 +0000 (GMT) (envelope-from rik@cronyx.ru) Received: (from root@localhost) by hanoi.cronyx.ru id i7ICl4tt037086 for current@freebsd.org.checked; (8.12.8/vak/2.1) Wed, 18 Aug 2004 16:47:04 +0400 (MSD) (envelope-from rik@cronyx.ru) Received: from cronyx.ru (hi.cronyx.ru [144.206.181.94]) by hanoi.cronyx.ru with ESMTP id i7ICjonA037020; (8.12.8/vak/2.1) Wed, 18 Aug 2004 16:45:50 +0400 (MSD) (envelope-from rik@cronyx.ru) Message-ID: <41234FC6.1000005@cronyx.ru> Date: Wed, 18 Aug 2004 16:47:02 +0400 From: Roman Kurakin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031208 X-Accept-Language: en-us, en MIME-Version: 1.0 To: drhodus@machdep.com References: <200408160104.03708.chris@behanna.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: chris@behanna.org cc: current@freebsd.org Subject: Re: Public Access to Perforce? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Aug 2004 12:50:09 -0000 David Rhodus wrote: >On Mon, 16 Aug 2004 01:04:03 -0400, Chris BeHanna wrote: > > >> Forgive me if this already exists. I searched the list archives, >>google, and freebsd.org and did not find any way for non-committers to >>have read-only access to the p4 repo. >> >> Is there a read-only account that the general public could use? >> >> > >With the perforce trees being hidden away without public access to the >changes, this makes the FreeBSD project no longer an open source >project. > > This hides only development proccess, not a stable result. If you don't have access to my home disks were I keep my intermediate code with additional debug/hacks and so on while I am debuggin new functionality would affect open source status of results of my work? rik