From owner-freebsd-current@FreeBSD.ORG Wed Aug 18 15:52:02 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 7316E16A4CE for ; Wed, 18 Aug 2004 15:52:02 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21EE843D39 for ; Wed, 18 Aug 2004 15:52:02 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i7IFo5Us057599; Wed, 18 Aug 2004 11:50:05 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i7IFo5wK057596; Wed, 18 Aug 2004 11:50:05 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 18 Aug 2004 11:50:05 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: drhodus@machdep.com In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 15:52:02 -0000 On Wed, 18 Aug 2004, Robert Watson wrote: > The unavailability of the perforce.freebsd.org web site is due to bugs > in the older version of the Perforce web server, and that the software > has not yet been upgraded. Hopefully that will be fixed soon, as that > site was beneficial to everyone. However, I'm having trouble thinking > of much or any on-going work in Perforce that doesn't get merged rapidly > or made available via other means. If there's specific work you are > interested in that isn't exported, I can make it available to you > easily. I believe the general purpose submit list is also subscribable, > although the volume of local changes is extremely high due to their "in > progress" nature. As has been pointed out, the comment about inavailability is now correct: the web site is back online again. The set of front page subtrees could use some updating though, the netperf_socket branch is no longer the are where most netperf work is happening -- it now happens in rwatson_netperf. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research