Fwd: t/47153851 GCC 10.2 Released

Fwd: t/47153851 GCC 10.2 Released

[Ian Lance Taylor]

I've checked internally at Google, and nobody has any idea why this is
happening.

The next step would seem to be to find all the @google.com addresses
on the gcc-announce mailing list, in the hopes that one of them will
be the trigger for these messages.  Since the switch to mailman I no
longer know how to see the members of a mailing list.  Could someone
either point me at some docs for how to do that, or send me a list of
the members on gcc-announce with an address @google.com?  Thanks.

Ian

---------- Forwarded message ---------
From: Jonathan Wakely via Gcc <gcc@gcc.gnu.org>
Date: Thu, Jul 23, 2020 at 4:18 AM
Subject: Re: t/47153851 GCC 10.2 Released
To: Google Ticket System <ext-ticket@google.com>
Cc: gcc@gcc.gnu.org <gcc@gcc.gnu.org>


Could somebody at Google please turn this crap off.

It might be confused by the change in the List-Id headers a few months
ago, but whatever the reason, please stop it.

On Thu, 23 Jul 2020 at 08:56, Google Ticket System via Gcc
<gcc@gcc.gnu.org> wrote:
>
> You have been CC'd on a Google Ticket                       The GNU Compiler Collection version 10.2 has been released.
>
> GCC 10.2 is a bug-fix release from the GCC 10 branch
> containing important fixes for regressions and serious bugs in
> GCC 10.1 with more than 94 bugs fixed since the previous release.
>
> This release is available from the FTP servers listed at:
>
> http://www.gnu.org/order/ftp.html
>
> Please do not contact me directly regarding questions or comments
> about this release.  Instead, use the resources available from
> http://gcc.gnu.org.
>
> As always, a vast number of people contributed to this GCC release
> -- far too many to thank them individually!
>           Reply to this email to update this ticket.

Re: Fwd: t/47153851 GCC 10.2 Released

[Frank Ch. Eigler]

Hi -

> The next step would seem to be to find all the @google.com addresses
> on the gcc-announce mailing list, in the hopes that one of them will
> be the trigger for these messages.  Since the switch to mailman I no
> longer know how to see the members of a mailing list.  [...]

# /usr/lib/mailman/bin/list_members  gcc-announce

Sending actual list off-list.

- FChE

Re: t/47153851 GCC 10.2 Released

[Jonathan Wakely]

I already said this to Ian and Frank, but for the list's benefit:

Richi already removed the suspected culprit from the gcc-announce
subscriber list. Hopefully it's resolved now.

On Fri, 24 Jul 2020 at 18:51, Ian Lance Taylor <iant@google.com> wrote:
>
> I've checked internally at Google, and nobody has any idea why this is
> happening.
>
> The next step would seem to be to find all the @google.com addresses
> on the gcc-announce mailing list, in the hopes that one of them will
> be the trigger for these messages.  Since the switch to mailman I no
> longer know how to see the members of a mailing list.  Could someone
> either point me at some docs for how to do that, or send me a list of
> the members on gcc-announce with an address @google.com?  Thanks.
>
> Ian
>
> ---------- Forwarded message ---------
> From: Jonathan Wakely via Gcc <gcc@gcc.gnu.org>
> Date: Thu, Jul 23, 2020 at 4:18 AM
> Subject: Re: t/47153851 GCC 10.2 Released
> To: Google Ticket System <ext-ticket@google.com>
> Cc: gcc@gcc.gnu.org <gcc@gcc.gnu.org>
>
>
> Could somebody at Google please turn this crap off.
>
> It might be confused by the change in the List-Id headers a few months
> ago, but whatever the reason, please stop it.
>
> On Thu, 23 Jul 2020 at 08:56, Google Ticket System via Gcc
> <gcc@gcc.gnu.org> wrote:
> >
> > You have been CC'd on a Google Ticket                       The GNU Compiler Collection version 10.2 has been released.
> >
> > GCC 10.2 is a bug-fix release from the GCC 10 branch
> > containing important fixes for regressions and serious bugs in
> > GCC 10.1 with more than 94 bugs fixed since the previous release.
> >
> > This release is available from the FTP servers listed at:
> >
> > http://www.gnu.org/order/ftp.html
> >
> > Please do not contact me directly regarding questions or comments
> > about this release.  Instead, use the resources available from
> > http://gcc.gnu.org.
> >
> > As always, a vast number of people contributed to this GCC release
> > -- far too many to thank them individually!
> >           Reply to this email to update this ticket.