From owner-freebsd-current Thu Apr 8 19: 3:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id DC76914CAB for ; Thu, 8 Apr 1999 19:03:49 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id WAA13233; Thu, 8 Apr 1999 22:01:32 -0400 (EDT) Message-ID: <19990408220132.A12977@netmonger.net> Date: Thu, 8 Apr 1999 22:01:32 -0400 From: Christopher Masto To: Sheldon Hearn Cc: current@freebsd.org Subject: Re: UPDATING needs updating References: <19990408142419.A24545@netmonger.net> <63587.923622867@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <63587.923622867@axl.noc.iafrica.com>; from Sheldon Hearn on Fri, Apr 09, 1999 at 03:54:27AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 09, 1999 at 03:54:27AM +0200, Sheldon Hearn wrote: > > > On Thu, 08 Apr 1999 14:24:19 -0400, Christopher Masto wrote: > > > Mightn't it be a good idea to mention the egcs move in /usr/src/UPDATING? > > Now that both bootstrapping and -j8 seem to be working, it wouldn't be > very useful. Not very useful to tell people about the first major compiler change in years? It may not break "make world", but it certainly breaks things like C++ library compatability and a large part of the ports collection. Suprises should be documented. -current users should be reading -current, but that doesn't mean someone might not join after the egcs discussion. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message