From owner-freebsd-current Sun Sep 1 22:56:52 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B015D37B400; Sun, 1 Sep 2002 22:56:44 -0700 (PDT) Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B1ED43E4A; Sun, 1 Sep 2002 22:56:44 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id g825ubv14816; Sun, 1 Sep 2002 22:56:37 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Sun, 1 Sep 2002 22:56:37 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Scott Long Cc: Peter Wemm , current@freebsd.org, developers@freebsd.org Subject: Re: HEADS UP: GCC 3.2 in progress In-Reply-To: <20020902004142.GA5862@hollin.btc.adaptec.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Thank you. Let's move on. On Sun, 1 Sep 2002, Scott Long wrote: > On Sun, Sep 01, 2002 at 05:12:43PM -0700, Matthew Jacob wrote: > > > > > > [...] > > > > > > Of course. And being accused of 'trolling' is also a learning > > experience. > > Ok, I apologize for calling you a 'troll'. I certainly didn't mean > it in the context of what's going on in other mailing lists, and it > probably wasn't appropriate in any context. Please note, hovever, > that many of the concerns that you've brought up in this thread > have been *heavily* discussed in the public mailing list over the > past month. Just two weeks ago there was a heated discussion over > whether to import gcc 3.2, or leapfrog it and wait for 3.3. There > have been many more discussions like it. > > Scott > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message