This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: RFC: libc-testresults mailing list

From: Joseph Myers <joseph at codesourcery dot com>
To: Andrew Pinski <pinskia at gmail dot com>
Cc: Carlos O'Donell <carlos at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>
Date: Thu, 3 Nov 2016 13:21:30 +0000
Subject: Re: RFC: libc-testresults mailing list
Authentication-results: sourceware.org; auth=none
References: <alpine.DEB.2.20.1611021254190.29297@digraph.polyomino.org.uk> <df1d2a90-bf16-87e9-a14a-02c73051fe14@redhat.com> <alpine.DEB.2.20.1611021639370.18772@digraph.polyomino.org.uk> <CA+=Sn1=vv6ztAHuZ-eFsvVD7FLOa1QUdJnCCO0acTrFTaEP1kw@mail.gmail.com>

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

References:
- RFC: libc-testresults mailing list
  - From: Joseph Myers
- Re: RFC: libc-testresults mailing list
  - From: Carlos O'Donell
- Re: RFC: libc-testresults mailing list
  - From: Joseph Myers
- Re: RFC: libc-testresults mailing list
  - From: Andrew Pinski

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]