public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "h2+bugs at fsfe dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/103904] [defect fix] Please backport P2325R3 to 10 and 11 Date: Tue, 08 Feb 2022 15:53:26 +0000 [thread overview] Message-ID: <bug-103904-4-V0fhzURNeI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103904-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103904 --- Comment #8 from Hannes Hauswedell <h2+bugs at fsfe dot org> --- Hi, I wanted to ask politely whether you have discussed this issue and came to a conclusion? It if it is still being discussed, can you at least "confirm" this issue and put it on some list for the next patch-level releases? Otherwise, it will be forgotten. And the longer we wait with a decision, the less likely it will be that it can be backported. Thank you!
next prev parent reply other threads:[~2022-02-08 15:53 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-04 15:22 [Bug c++/103904] New: " h2+bugs at fsfe dot org 2022-01-04 15:45 ` [Bug libstdc++/103904] " redi at gcc dot gnu.org 2022-01-04 15:46 ` redi at gcc dot gnu.org 2022-01-04 15:51 ` redi at gcc dot gnu.org 2022-01-04 15:55 ` h2+bugs at fsfe dot org 2022-01-04 16:13 ` redi at gcc dot gnu.org 2022-01-04 17:13 ` h2+bugs at fsfe dot org 2022-01-05 8:42 ` rguenth at gcc dot gnu.org 2022-02-08 15:53 ` h2+bugs at fsfe dot org [this message] 2022-02-08 16:30 ` redi at gcc dot gnu.org 2022-02-08 16:54 ` redi at gcc dot gnu.org 2022-02-08 20:58 ` h2+bugs at fsfe dot org 2022-02-11 14:04 ` cvs-commit at gcc dot gnu.org 2022-02-11 14:04 ` cvs-commit at gcc dot gnu.org 2022-02-11 14:04 ` cvs-commit at gcc dot gnu.org 2022-02-11 20:40 ` cvs-commit at gcc dot gnu.org 2022-05-31 18:39 ` cvs-commit at gcc dot gnu.org 2022-05-31 18:39 ` cvs-commit at gcc dot gnu.org 2022-05-31 18:49 ` ppalka at gcc dot gnu.org 2022-05-31 19:50 ` h2+bugs at fsfe 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-103904-4-V0fhzURNeI@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).