From owner-freebsd-current Thu Mar 12 21:33:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25849 for freebsd-current-outgoing; Thu, 12 Mar 1998 21:33:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25843 for ; Thu, 12 Mar 1998 21:33:57 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.8.8/8.8.5) id VAA27472; Thu, 12 Mar 1998 21:35:20 -0800 (PST) From: Steve Kargl Message-Id: <199803130535.VAA27472@troutmask.apl.washington.edu> Subject: Re: C++ libs are broken In-Reply-To: from Brian Feldman at "Mar 12, 98 11:52:35 pm" To: green@feldman.dyn.ml.org (Brian Feldman) Date: Thu, 12 Mar 1998 21:35:19 -0800 (PST) Cc: chuckr@glue.umd.edu, green@feldman.dyn.ml.org, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Brian Feldman: > Yes, you're right. I was quite miffed when I wrote that message. It's just > that 3.0 can be so stable, and working, I hate to see it get messed up all > the time. Some people really take too much liberty committing any change > they want. I know right now, Alpha stuff, ELF stuff, and soft-updates > (bleh, it's SO unstable!), are getting worked on, but I think people > really do need to test their changes and compile to make sure they didn't If you're not prepared to run -current, then you should be running either 2.2.5 or -stable. > break anything like this. I really should read commit mail, but I have no > good mail box to use, since this is just my dynamic IP'd 28.8 part-time If you don't have time to scan the commit mail, then you definitely shouldn't be running -current. > dial-up anyway. *sigh* I need to go send a pr, because mounted > synchronously, mount's output shows my drives with async (!) and sync > write.... majorly weird. Maybe we need to get softupdates backed out a > bit. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message