From owner-freebsd-current@FreeBSD.ORG  Mon Aug 16 05:04:01 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 2B80816A4CE
	for <current@freebsd.org>; Mon, 16 Aug 2004 05:04:01 +0000 (GMT)
Received: from bittern.mail.pas.earthlink.net (bittern.mail.pas.earthlink.net
	[207.217.120.119])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E2CE943D5D
	for <current@freebsd.org>; Mon, 16 Aug 2004 05:04:00 +0000 (GMT)
	(envelope-from chris@behanna.org)
Received: from oh-65-40-131-183.sta.sprint-hsd.net ([65.40.131.183]
	helo=[192.168.168.11])
	by bittern.mail.pas.earthlink.net with esmtp (Exim 3.33 #1)
	id 1BwZf6-0007KT-00
	for current@freebsd.org; Sun, 15 Aug 2004 22:04:00 -0700
From: Chris BeHanna <chris@behanna.org>
Organization: Western Pennsylvania Pizza Disposal Unit
To: current@freebsd.org
Date: Mon, 16 Aug 2004 01:04:03 -0400
User-Agent: KMail/1.6.2
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <200408160104.03708.chris@behanna.org>
Subject: Public Access to Perforce?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: chris@behanna.org
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Aug 2004 05:04:01 -0000

    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?

    To alleviate load on perforce.freebsd.org, p4proxy could be set up
on the current cvsup mirrors.  I'd likely set up my own proxy server
on my home box, just to improve local response time (and ease setting
up a local vendor branch for playing around).

Thanks,
-- 
Chris BeHanna
Software Engineer                   (Remove "bogus" before responding.)
chris@bogus.behanna.org
                 Turning coffee into software since 1990.