From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16621 invoked by alias); 26 Jun 2009 17:01:09 -0000 Received: (qmail 16415 invoked by uid 22791); 26 Jun 2009 17:01:08 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from troutmask.apl.washington.edu (HELO troutmask.apl.washington.edu) (128.208.78.105) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 26 Jun 2009 17:01:01 +0000 Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.3/8.14.3) with ESMTP id n5QH0pca080797; Fri, 26 Jun 2009 10:00:51 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.3/8.14.3/Submit) id n5QH0ptu080796; Fri, 26 Jun 2009 10:00:51 -0700 (PDT) (envelope-from sgk) Date: Fri, 26 Jun 2009 17:06:00 -0000 From: Steve Kargl To: Angelo Graziosi Cc: Kai Tietz , tprince@computer.org, Seiji Kachi , Dave Korn , GCC Subject: Re: Failure building current 4.5 snapshot on Cygwin Message-ID: <20090626170051.GA80586@troutmask.apl.washington.edu> References: <4A44A724.6040804@alice.it> <4A44B1F3.3010300@gmail.com> <4A44B3F7.4090401@alice.it> <4A44C865.1040800@mqe.biglobe.ne.jp> <90baa01f0906260619w6f6548eam2487b809028dd02e@mail.gmail.com> <4A44EC02.60003@sbcglobal.net> <90baa01f0906260917h28b4137fi730656b212ce16ab@mail.gmail.com> <20090626162831.GA80377@troutmask.apl.washington.edu> <4A44FC97.4020803@alice.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A44FC97.4020803@alice.it> User-Agent: Mutt/1.4.2.3i Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2009-06/txt/msg00615.txt.bz2 On Fri, Jun 26, 2009 at 06:51:35PM +0200, Angelo Graziosi wrote: > Steve Kargl ha scritto: > > > >Can you guys learn to trim the cc list? This issue > >has absoutely nothing to do with gfortran. Yet, > >fortan@gcc.gnu.org is being spammed with your email. > > Really... it was discovered because someone has the 'bad' habit to build > gfortran... :-) > If you actually read the text that you posted in your first email, you would have found that there is clearly no evidence that this failure is gfortran related. This then would have been a clear indication that cross-posting to fortran@ is unwelcomed. -- Steve