From owner-freebsd-current Fri Mar 13 02:17:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA01704 for freebsd-current-outgoing; Fri, 13 Mar 1998 02:17:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA01698 for ; Fri, 13 Mar 1998 02:17:29 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id CAA19165; Fri, 13 Mar 1998 02:15:44 -0800 (PST) To: Brian Feldman cc: Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: C++ libs are broken In-reply-to: Your message of "Thu, 12 Mar 1998 23:52:35 EST." Date: Fri, 13 Mar 1998 02:15:44 -0800 Message-ID: <19161.889784144@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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 Well, FWIW, we've talked before and I've already told you several times that I didn't think you should be running -current; you haven't got the prerequisites (you don't read the right mailing lists and you definitely shouldn't be out on the bleeding edge in general). I don't think -current should be blamed for inappropriate use here. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message