Date: Tue, 1 May 2001 18:58:48 -0500 From: "David W. Chapman Jr." <dwcjr@inethouston.net> To: <grasshacker@over-yonder.net>, "Jordan Hubbard" <jkh@osd.bsdi.com> Cc: <current@FreeBSD.ORG> Subject: Re: HEADS UP! bad bug in -current. Message-ID: <021701c0d29a$a9dcf2c0$931576d8@inethouston.net> References: <20010501191534.96E1A380C@overcee.netplex.com.au><20010501182359.A22707@over-yonder.net> <20010501165654K.jkh@osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
It was almost like that dirpref problem I ran into a few weeks ago, I upgraded from -stable to -current and I had to reinstall because of it, but this usually doesn't happen. ----- Original Message ----- From: "Jordan Hubbard" <jkh@osd.bsdi.com> To: <grasshacker@over-yonder.net> Cc: <current@FreeBSD.ORG> Sent: Tuesday, May 01, 2001 6:56 PM Subject: Re: HEADS UP! bad bug in -current. > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?021701c0d29a$a9dcf2c0$931576d8>