From owner-freebsd-current  Tue May  1 16:57: 6 2001
Delivered-To: freebsd-current@freebsd.org
Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98])
	by hub.freebsd.org (Postfix) with ESMTP id 20A7537B422
	for <current@FreeBSD.ORG>; Tue,  1 May 2001 16:57:04 -0700 (PDT)
	(envelope-from jkh@osd.bsdi.com)
Received: from localhost (jkh@localhost [127.0.0.1])
	by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f41Nus332880;
	Tue, 1 May 2001 16:56:54 -0700 (PDT)
	(envelope-from jkh@osd.bsdi.com)
To: grasshacker@over-yonder.net
Cc: current@FreeBSD.ORG
Subject: Re: HEADS UP! bad bug in -current.
In-Reply-To: <20010501182359.A22707@over-yonder.net>
References: <20010501191534.96E1A380C@overcee.netplex.com.au>
	<20010501182359.A22707@over-yonder.net>
X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010501165654K.jkh@osd.bsdi.com>
Date: Tue, 01 May 2001 16:56:54 -0700
From: Jordan Hubbard <jkh@osd.bsdi.com>
X-Dispatcher: imput version 20000228(IM140)
Lines: 8
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Say, FreeBSD is usually pretty safe, even in CURRENT.
> Has something near this magnitude of Really Bad Stuffage snuck into the
> codebase before?

No, it's not common, and it generally takes a Dane swinging something
sharp to inflict quite this much damage on our user base. ;-)

- Jordan

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