From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 80644 invoked by alias); 3 Nov 2016 13:21:51 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 80627 invoked by uid 89); 3 Nov 2016 13:21:50 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy=Hx-languages-length:687, interaction, gccregression, gcc-regression X-HELO: relay1.mentorg.com Date: Thu, 03 Nov 2016 13:21:00 -0000 From: Joseph Myers To: Andrew Pinski CC: Carlos O'Donell , GNU C Library Subject: Re: RFC: libc-testresults mailing list In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-ClientProxiedBy: svr-ies-mbx-02.mgc.mentorg.com (139.181.222.2) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) X-SW-Source: 2016-11/txt/msg00101.txt.bz2 On Wed, 2 Nov 2016, Andrew Pinski wrote: > > It would of course be expected that if someone's build system starts > > flooding the list with multiple mails from identical builds (keeping > > rebuilding the same versions continuously, or mail system problems > > resulting in duplicate mails) then those mails would be blocked until the > > problem is sorted out. > > We have had that issue once or twice but nothing in the last 2-3 years > as far as I know. gcc-regression, April this year, an interaction between IBM's mail system and sourceware resulted in 750 MB of mail to the list in a few days. -- Joseph S. Myers joseph@codesourcery.com