From owner-freebsd-current Thu Mar 12 12:09:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17592 for freebsd-current-outgoing; Thu, 12 Mar 1998 12:09:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17582 for ; Thu, 12 Mar 1998 12:09:32 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id UAA11613; Thu, 12 Mar 1998 20:09:20 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id VAA03700; Thu, 12 Mar 1998 21:09:19 +0100 (MET) Message-ID: <19980312210918.13360@follo.net> Date: Thu, 12 Mar 1998 21:09:18 +0100 From: Eivind Eklund To: Nathan Dorfman , current@FreeBSD.ORG Subject: Re: Slew of binutils commits lately References: <19980312145208.07230@rtfm.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980312145208.07230@rtfm.net>; from Nathan Dorfman on Thu, Mar 12, 1998 at 02:52:08PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 12, 1998 at 02:52:08PM -0500, Nathan Dorfman wrote: > Sorry if my question is redundant, but I have only had a working computer > for a week--my motherboard blew up over a month ago and I couldn't keep > track of all the FreeBSD news since all I had were the school 3.11/NetWare > computers. Anyway, I'm noticing an onslaught of updates with binutils these > past few days--what does this indicate? Anything monumental or earthshaking? Both alpha build support and i386 ELF support is going in at the same time. > Or are these just "routine" upgrades to binutils? Is it safe to cvsup and > make world in the middle of this conversion or should I wait until it's > complete? It seems to be safe; no reports of build-problems lately, at least. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message