public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: jakub@gcc.gnu.org
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: wwwdocs/htdocs/projects cxx-status.html
Date: Fri, 11 Jan 2019 18:21:00 -0000 [thread overview]
Message-ID: <20190111182148.75835.qmail@sourceware.org> (raw)
Files modified in the GCC repository. Log entry:
Add initial gcc-9/porting_to.html.
Some gcc-9/changes.html additions and mark std::is_constant_evaluated as
implemented for GCC9.
next reply other threads:[~2019-01-11 18:21 UTC|newest]
Thread overview: 98+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 18:21 jakub [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-14 21:30 jason
2019-09-10 18:01 jason
2019-08-29 3:24 mpolacek
2019-08-29 3:16 mpolacek
2019-08-28 20:38 mpolacek
2019-08-17 14:18 mpolacek
2019-08-12 18:55 mpolacek
2019-08-07 14:34 mpolacek
2019-08-06 16:25 mpolacek
2019-08-05 19:05 mpolacek
2019-08-05 16:54 mpolacek
2019-08-05 15:13 jakub
2019-08-05 13:47 mpolacek
2019-08-04 15:43 mpolacek
2019-08-04 15:42 mpolacek
2019-08-04 14:19 mpolacek
2019-07-08 17:45 mpolacek
2019-05-29 8:14 jakub
2019-04-29 22:10 gerald
2019-04-29 14:08 nathan
2019-04-18 15:29 jason
2019-03-01 15:39 jakub
2019-02-07 9:07 jakub
2019-01-28 22:39 jason
2019-01-28 22:38 jason
2019-01-21 17:23 jakub
2019-01-21 17:21 jakub
2019-01-11 19:07 jason
2018-12-01 17:59 mpolacek
2018-11-28 21:42 mpolacek
2018-11-19 19:21 jason
2018-11-19 19:20 jason
2018-11-16 21:50 jason
2018-11-14 16:48 jakub
2018-11-13 21:17 mpolacek
2018-11-13 20:44 mpolacek
2018-11-13 4:50 jason
2018-11-09 7:37 jason
2018-11-01 22:14 mpolacek
2018-10-30 20:02 mpolacek
2018-10-03 15:57 jason
2018-09-18 19:24 mpolacek
2018-09-10 8:36 gerald
2018-08-13 15:57 mpolacek
2018-07-31 14:22 jakub
2018-06-28 16:36 jason
2018-06-14 19:59 jakub
2018-06-12 23:12 mpolacek
2018-06-01 22:47 jason
2018-05-31 18:33 jason
2018-05-23 16:54 mpolacek
2018-03-27 16:57 jason
2018-03-27 15:22 jason
2018-03-23 20:30 jakub
2018-03-23 20:26 jakub
2018-03-23 20:08 jakub
2017-11-30 4:20 jason
2017-09-11 17:20 redi
2017-04-11 22:28 gerald
2017-03-16 21:18 jason
2017-01-28 22:21 gerald
2017-01-09 21:51 jason
2016-12-22 20:29 jason
2016-12-21 22:16 jason
2016-12-08 8:28 jakub
2016-11-15 5:21 jason
2016-11-09 20:04 jason
2016-11-07 23:13 jason
2016-11-02 1:51 jason
2016-10-17 16:15 jason
2016-10-13 20:43 jakub
2016-10-05 23:01 jason
2016-10-05 18:05 mpolacek
2016-10-05 14:17 jason
2016-09-29 20:56 jakub
2016-09-27 20:00 jakub
2016-09-27 15:46 jason
2016-09-26 17:02 jakub
2016-09-26 15:56 mpolacek
2016-09-23 17:41 jakub
2016-09-13 19:34 jakub
2016-09-13 1:38 jason
2016-08-29 20:16 jason
2016-08-09 4:34 jason
2016-08-05 18:24 jason
2016-08-04 14:16 jason
2016-05-02 21:24 jason
2016-05-02 21:23 jason
2016-04-28 21:33 jason
2016-04-05 16:00 gerald
2016-04-05 15:39 gerald
2016-04-05 13:26 jason
2016-04-04 4:50 gerald
2016-04-02 13:44 gerald
2016-04-02 10:45 gerald
2016-04-02 10:39 gerald
2016-04-02 10:03 gerald
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=20190111182148.75835.qmail@sourceware.org \
--to=jakub@gcc.gnu.org \
--cc=gcc-cvs-wwwdocs@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).