From owner-cvs-all  Sat Jan 16 00:20:42 1999
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA18655
          for cvs-all-outgoing; Sat, 16 Jan 1999 00:20:42 -0800 (PST)
          (envelope-from owner-cvs-all@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18647
          for <committers@FreeBSD.ORG>; Sat, 16 Jan 1999 00:20:38 -0800 (PST)
          (envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
	by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id AAA99095;
	Sat, 16 Jan 1999 00:19:43 -0800 (PST)
To: "Daniel O'Callaghan" <danny@hilink.com.au>
cc: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, committers@FreeBSD.ORG
Subject: Re: Y2K compliance question 
In-reply-to: Your message of "Fri, 15 Jan 1999 12:36:52 +1100."
             <Pine.BSF.3.96.990115122736.2001D-100000@enya.clari.net.au> 
Date: Sat, 16 Jan 1999 00:19:43 -0800
Message-ID: <99092.916474783@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk

> Right now, FreeBSD-current is *NOT* y2k compliant.  I know that there
> *are* bugs remaining.

It would help vastly if you could be more specific.  Saying, for
example, that you found "problems" or that there were "beasties"
lurking aren't technically detailed enough to be useful.

- Jordan

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