From owner-freebsd-current@FreeBSD.ORG Wed Aug 18 18:02:24 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 2155116A4CF for ; Wed, 18 Aug 2004 18:02:24 +0000 (GMT) Received: from swan.mail.pas.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA1E043D58 for ; Wed, 18 Aug 2004 18:02:23 +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 swan.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 1BxUlT-0005AS-00 for current@freebsd.org; Wed, 18 Aug 2004 11:02:23 -0700 From: Chris BeHanna Organization: Western Pennsylvania Pizza Disposal Unit To: current@freebsd.org Date: Wed, 18 Aug 2004 14:03:00 -0400 User-Agent: KMail/1.6.2 References: <200408160104.03708.chris@behanna.org> <20040816060528.GA2065@empiric.icir.org> In-Reply-To: <20040816060528.GA2065@empiric.icir.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200408181403.00873.chris@behanna.org> Subject: Re: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Aug 2004 18:02:24 -0000 On Monday 16 August 2004 02:05, Bruce M Simpson wrote: > On Mon, Aug 16, 2004 at 01:04:03AM -0400, Chris BeHanna wrote: > > Is there a read-only account that the general public could use? > > I think this is an excellent idea. Perhaps one should be set up. I wish. OpenWatcom has guest Perforce access, for example. > > 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). > > Now I'm curious about doing this myself! It would certainly help on > my laptop. I am lagging behind on -CURRENT at the moment. It is dirt simple to set up a p4proxy. The disk space that is required is constrained to the size of the master p4 repo, so that is a consideration (this will likely be several GB). Personally, I'd donate to the maintainer of cvsup11 (the closest node to me) to provide disk space for this if it became available. Atomic commits, always up-to-date. *Wonderful*. Even for committers, it'd be great, because the proxies are write-through (for accounts that have write access). -- Chris BeHanna Software Engineer (Remove "bogus" before responding.) chris@bogus.behanna.org Turning coffee into software since 1990.