From owner-freebsd-bugs@FreeBSD.ORG  Sun Apr 11 11:53:17 2010
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 424A01065670;
	Sun, 11 Apr 2010 11:53:17 +0000 (UTC)
	(envelope-from gavin@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 16AE18FC17;
	Sun, 11 Apr 2010 11:53:17 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o3BBrGj9094574;
	Sun, 11 Apr 2010 11:53:16 GMT
	(envelope-from gavin@freefall.freebsd.org)
Received: (from gavin@localhost)
	by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o3BBrGgx094570;
	Sun, 11 Apr 2010 11:53:16 GMT (envelope-from gavin)
Date: Sun, 11 Apr 2010 11:53:16 GMT
Message-Id: <201004111153.o3BBrGgx094570@freefall.freebsd.org>
To: j.porter.clark@nasa.gov, gavin@FreeBSD.org, freebsd-bugs@FreeBSD.org
From: gavin@FreeBSD.org
Cc: 
Subject: Re: misc/138679: [mirrors] Current 7.2-STABLE i386 kernel won't
	build: cvsup17.us.freebsd.org is behind
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Apr 2010 11:53:17 -0000

Synopsis: [mirrors] Current 7.2-STABLE i386 kernel won't build: cvsup17.us.freebsd.org is behind

State-Changed-From-To: open->closed
State-Changed-By: gavin
State-Changed-When: Sun Apr 11 11:51:35 UTC 2010
State-Changed-Why: 
This was resolved some months ago.  Thanks for your report, however the PR
database is not really the best place to report such "infrastructure" issues -
it is primarily for bugs/enhancement requests etc in FreeBSd itself, or the
ports tree that comes as part of FreeBSD.  The mailing lists are generally the
best place to bring such "infrastructure" issues up.

http://www.freebsd.org/cgi/query-pr.cgi?pr=138679