From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [committed] libstdc++: Update C++17 status table for <charconv>
Date: Tue, 2 Feb 2021 10:14:44 +0000 [thread overview]
Message-ID: <20210202101444.GA49261@redhat.com> (raw)
In-Reply-To: <20210201160802.GA11158@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 517 bytes --]
On 01/02/21 16:08 +0000, Jonathan Wakely wrote:
>libstdc++-v3/ChangeLog:
>
> * doc/xml/manual/status_cxx2011.xml: Update std::call_once
> status.
> * doc/xml/manual/status_cxx2014.xml: Likewise.
> * doc/xml/manual/status_cxx2017.xml: Likewise. Update
> std::from_chars and std::to_chars status. Fix formatting.
> * doc/html/manual/status.html: Regenerate.
I noticed we have an unwanted extra column at the right of the
C++11/14/17 tables, due to a stray <entry/> element. Fixed by this
patch.
Committed to trunk.
[-- Attachment #2: patch.txt --]
[-- Type: text/x-patch, Size: 2111 bytes --]
commit 886f9f519c0c6297c95887839e318fa79cba2052
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Tue Feb 2 09:55:52 2021
libstdc++: Fix markup for status tables in docs
libstdc++-v3/ChangeLog:
* doc/xml/manual/status_cxx2011.xml: Remove stray table cell.
* doc/xml/manual/status_cxx2014.xml: Likewise.
* doc/xml/manual/status_cxx2017.xml: Likewise.
* doc/html/manual/status.html: Regenerate.
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2011.xml b/libstdc++-v3/doc/xml/manual/status_cxx2011.xml
index e13ca566ea3..be873962597 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx2011.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx2011.xml
@@ -2174,7 +2174,6 @@ particular release.
<entry>Class template <code>regex_traits</code></entry>
<entry>Partial</entry>
<entry><code>transform_primary</code> is not correctly implemented</entry>
- <entry/>
</row>
<row>
<entry>28.8</entry>
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2014.xml b/libstdc++-v3/doc/xml/manual/status_cxx2014.xml
index 7b2d4603b24..61bea5adad5 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx2014.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx2014.xml
@@ -1142,7 +1142,6 @@ not in any particular release.
<entry>Class template <code>regex_traits</code></entry>
<entry>Partial</entry>
<entry><code>transform_primary</code> is not correctly implemented</entry>
- <entry/>
</row>
<row>
<entry>28.8</entry>
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2017.xml b/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
index 7b5df3d1385..aa34b8c3cf5 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
@@ -2224,7 +2224,6 @@ since C++14 and the implementation is complete.
<entry>Class template <code>regex_traits</code></entry>
<entry>Partial</entry>
<entry><code>transform_primary</code> is not correctly implemented</entry>
- <entry/>
</row>
<row>
<entry>31.8</entry>
prev parent reply other threads:[~2021-02-02 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 16:08 Jonathan Wakely
2021-02-02 10:14 ` 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=20210202101444.GA49261@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).