From owner-freebsd-current Thu Jun 6 10:17:15 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 4EDA337B400 for ; Thu, 6 Jun 2002 10:17:10 -0700 (PDT) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.3/8.12.2) with ESMTP id g56HHAJn089188; Thu, 6 Jun 2002 10:17:10 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.3/8.12.3/Submit) id g56HH9HR089187; Thu, 6 Jun 2002 10:17:09 -0700 (PDT) Date: Thu, 6 Jun 2002 10:17:09 -0700 From: "David O'Brien" To: Christopher Nehren Cc: current@freebsd.org Subject: Re: "Safe" to go to -CURRENT? Message-ID: <20020606101709.H59829@dragon.nuxi.com> Reply-To: obrien@freebsd.org Mail-Followup-To: David O'Brien , Christopher Nehren , current@freebsd.org References: <1023266819.500.6.camel@prophecy.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1023266819.500.6.camel@prophecy.dyndns.org>; from apeiron@prophecy.dyndns.org on Wed, Jun 05, 2002 at 08:46:59AM +0000 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Jun 05, 2002 at 08:46:59AM +0000, Christopher Nehren wrote: > I've been monitoring the -CURRENT mailing list for about a day or two, > and haven't seen anything that's really broken (except for GCC 3.x, > which I don't use anyway). So, is it "safe" to upgrade to -CURRENT yet? > TIA for the info, You use C to rebuild your system -- so I would say you _do_ use(will) use GCC 3.x. The C compiler has been fine since day 1. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message