From owner-freebsd-current  Sat Mar 25 12:14:21 2000
Delivered-To: freebsd-current@freebsd.org
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
	by hub.freebsd.org (Postfix) with ESMTP id 2AE0337B851
	for <current@freebsd.org>; Sat, 25 Mar 2000 12:14:19 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA04731;
	Sat, 25 Mar 2000 12:15:21 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
To: Jonathan Lemon <jlemon@flugsvamp.com>
Cc: current@freebsd.org
Subject: Re: Somebody broke alpha kernel builds? 
In-reply-to: Your message of "Sat, 25 Mar 2000 14:09:24 CST."
             <200003252009.OAA20866@prism.flugsvamp.com> 
Date: Sat, 25 Mar 2000 12:15:21 -0800
Message-ID: <4728.954015321@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Speaking of which, why is /home/ncvs on beast not pointing to 
> the current CVS repository?  I got bit by the same error after
> doing (what I thought) was a correct `cvs update' on beast.

Sorry, "my bad"; the alpha releases were falling over on some sort of
NFS bogon (and cvs checkouts using ssh weren't working either) so I
was forced to copy the repository over to /j on beast and start using
cvsup to synchronize it.  Now that 4.0-RELEASE is behind us and we
don't have another coming up for a few months, I'll point it back.
Done!

- Jordan


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message