public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: overseers@gcc.gnu.org
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>
Subject: Fwd: t/47153851 GCC 10.2 Released
Date: Fri, 24 Jul 2020 10:51:24 -0700	[thread overview]
Message-ID: <CAKOQZ8y4OnFt9_Mue9jZ7f3OvZO-B9omGPHEAjB13KxxB6RJhA@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdTZ2wwr0Dg25YYLfG4wcYkhm39xfLpFB-tZfW=19FojwA@mail.gmail.com>

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.

       reply	other threads:[~2020-07-24 17:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1835188000.10606029.1595488810294@guts-prod-remedy16.vm.corp.google.com>
     [not found] ` <CAH6eHdTZ2wwr0Dg25YYLfG4wcYkhm39xfLpFB-tZfW=19FojwA@mail.gmail.com>
2020-07-24 17:51   ` Ian Lance Taylor [this message]
2020-07-24 18:10     ` Frank Ch. Eigler
2020-07-24 20:13     ` Jonathan Wakely

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKOQZ8y4OnFt9_Mue9jZ7f3OvZO-B9omGPHEAjB13KxxB6RJhA@mail.gmail.com \
    --to=iant@google.com \
    --cc=jwakely.gcc@gmail.com \
    --cc=overseers@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).