From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Document C++20 library status
Date: Tue, 15 Jan 2019 10:34:00 -0000 [thread overview]
Message-ID: <20190115103437.GN15627@redhat.com> (raw)
In-Reply-To: <20190111234215.GA16883@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 371 bytes --]
On 11/01/19 23:42 +0000, Jonathan Wakely wrote:
> * doc/xml/manual/intro.xml: Include new section.
> * doc/xml/manual/status_cxx2017.xml: Document more
> implementation-defined properties of the library.
> * doc/xml/manual/status_cxx2020.xml: Document C++2a status.
> * doc/html/*: Regenerate.
P1123R0 needs no changes, so can be marked complete.
Committed to trunk.
[-- Attachment #2: patch.txt --]
[-- Type: text/x-patch, Size: 975 bytes --]
commit bdcb89e8673c5f1d8f799651984a0afc5fcb8a20
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Tue Jan 15 10:33:33 2019 +0000
* doc/xml/manual/status_cxx2020.xml: Update P1123R0 status.
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2020.xml b/libstdc++-v3/doc/xml/manual/status_cxx2020.xml
index 67353850ce5..05d34284506 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx2020.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx2020.xml
@@ -848,14 +848,13 @@ Feature-testing recommendations for C++</link>.
</row>
<row>
- <?dbhtml bgcolor="#C8B0B0" ?>
<entry> Editorial Guidance for merging P0019r8 and P0528r3 </entry>
<entry>
<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p1123r0.html">
P1123R0
</link>
</entry>
- <entry align="center"> </entry>
+ <entry align="center"> Note 1 </entry>
<entry />
</row>
prev parent reply other threads:[~2019-01-15 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 23:42 Jonathan Wakely
2019-01-15 10:34 ` Jonathan Wakely [this message]
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=20190115103437.GN15627@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).