public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/21772] exception safety testing Date: Tue, 16 May 2023 19:41:11 +0000 [thread overview] Message-ID: <bug-21772-4-u2GqxfQzF8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-21772-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21772 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bkoz at gcc dot gnu.org |unassigned at gcc dot gnu.org Status|ASSIGNED |NEW --- Comment #24 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Unassigning since Benjamin since not been active in GCC development for over 8 years now.
next parent reply other threads:[~2023-05-16 19:41 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-21772-4@http.gcc.gnu.org/bugzilla/> 2023-05-16 19:41 ` pinskia at gcc dot gnu.org [this message] [not found] <bug-21772-365@http.gcc.gnu.org/bugzilla/> 2009-12-16 3:34 ` bkoz at gcc dot gnu dot org 2009-12-16 3:36 ` bkoz at gcc dot gnu dot org 2009-12-16 5:17 ` bkoz at gcc dot gnu dot org 2009-12-16 10:14 ` paolo dot carlini at oracle dot com 2009-12-16 11:14 ` jwakely dot gcc at gmail dot com 2009-12-17 8:18 ` bkoz at gcc dot gnu dot org 2009-12-17 9:37 ` bkoz at gcc dot gnu dot org 2009-12-17 9:58 ` paolo dot carlini at oracle dot com 2010-01-01 3:39 ` bkoz at gcc dot gnu dot org 2010-01-01 3:55 ` bkoz at gcc dot gnu dot org 2010-01-01 10:14 ` paolo dot carlini at oracle dot com 2010-01-01 10:46 ` paolo dot carlini at oracle dot com 2010-01-01 11:03 ` paolo dot carlini at oracle dot com 2010-02-19 10:49 ` paolo dot carlini at oracle dot com 2010-03-04 12:00 ` paolo dot carlini at oracle dot com
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-21772-4-u2GqxfQzF8@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).