public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88323] implement C++20 language features.
Date: Fri, 13 Nov 2020 18:42:46 +0000	[thread overview]
Message-ID: <bug-88323-4-iv6rDpxFRO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-88323-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88323
Bug 88323 depends on bug 91367, which changed state.

Bug 91367 Summary: Implement P1099R5: using enum
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91367

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

  parent reply	other threads:[~2020-11-13 18:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-88323-4@http.gcc.gnu.org/bugzilla/>
2020-06-24  0:44 ` jason at gcc dot gnu.org
2020-08-03 23:10 ` mpolacek at gcc dot gnu.org
2020-08-31 20:12 ` mpolacek at gcc dot gnu.org
2020-09-03 18:32 ` mpolacek at gcc dot gnu.org
2020-09-09 22:06 ` jason at gcc dot gnu.org
2020-09-25 23:59 ` mpolacek at gcc dot gnu.org
2020-11-13 18:42 ` jason at gcc dot gnu.org [this message]
2020-11-13 18:44 ` jason at gcc dot gnu.org
2020-11-13 18:45 ` jakub at gcc dot gnu.org
2020-11-15 17:10 ` jason at gcc dot gnu.org
2021-08-17 19:21 ` jakub at gcc dot gnu.org
2021-09-01 19:35 ` jakub at gcc dot gnu.org
2022-09-08 18:37 ` redi at gcc dot gnu.org
2024-05-01 10:25 ` romain.geissler at amadeus dot com
2024-05-01 11:11 ` redi at gcc dot gnu.org
2024-05-01 14:46 ` jason at gcc dot gnu.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-88323-4-iv6rDpxFRO@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: 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).