From owner-freebsd-current Mon May 18 22:51:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19092 for freebsd-current-outgoing; Mon, 18 May 1998 22:51:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from m2.findmail.com (m2.findmail.com [209.185.96.135]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA19001 for ; Mon, 18 May 1998 22:51:17 -0700 (PDT) (envelope-from brianfeldman@hotmail.com) Received: (qmail 22618 invoked by uid 505); 19 May 1998 04:03:16 -0000 Date: 19 May 1998 04:03:16 -0000 Message-ID: <19980519040316.22617.qmail@m2.findmail.com> From: "Brian Feldman" Subject: Re: Next 3.0 SNAP CD coming up. In-Reply-To: <17583.895518409@time.cdrom.com> To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alrighty, here are two: 1) figure out why the heck my machine which was last up a week can now only stay up about 17 hours (!), repeatedly (I'll let you know if this stops, or if I can figure it out at all, but this is hour 11, and I don't know if it might have stopped... if it happens again I'll provide full details) 2) Can anyone think of one good reason not to have gcc go -pipe by default? It would make some sense to do so, and then to add a -nopipe switch, seeing that there should be no reasons not to use -pipe in 100% of the situations with using all pipeable tools, cpp, gcc, and gas. Any reason not to? If I get the go-ahead, I'll submit the patch. Cheers, Brian Feldman > Well, it's been 3 months since the last one so our next 3.0 SNAP CD is > now coming up for its scheduled production date. 3.0 also seems pretty > SNAPable right now, but if there are any issues people want to resolve > there then I'll wait a few days before rolling it. Consider this a > "heads up!" > > - 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