From: "jwakely.gcc at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/29853] mattermost instance
Date: Fri, 28 Apr 2023 17:07:23 +0000 [thread overview]
Message-ID: <bug-29853-14326-rlURp9uB80@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29853-14326@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29853
Jonathan Wakely <jwakely.gcc at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jwakely.gcc at gmail dot com
--- Comment #1 from Jonathan Wakely <jwakely.gcc at gmail dot com> ---
(In reply to Andrew Pinski from comment #0)
> I hear the C++ GCC front-end folks are using an instance for their work.
Maybe you're thinking of the ISO C++ committee. I don't think there's one for
G++ (unless they're keeping it secret!)
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-04-28 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 18:07 [Bug Infrastructure/29853] New: " pinskia at gcc dot gnu.org
2023-04-28 17:07 ` jwakely.gcc at gmail dot com [this message]
2023-07-24 19:10 ` [Bug Infrastructure/29853] " fche at redhat dot com
2023-08-05 17:45 ` mark at klomp dot org
2024-02-07 20:59 ` mark at klomp dot org
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=bug-29853-14326-rlURp9uB80@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=overseers@sourceware.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).