public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. b04fd89cb8bc48bad63fb59c91400bbf70e1f510 Date: Wed, 28 Apr 2021 17:10:24 +0000 (GMT) [thread overview] Message-ID: <20210428171024.DEFD13AA1407@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via b04fd89cb8bc48bad63fb59c91400bbf70e1f510 (commit) from 24151c175c08222c268d9c37cc8fa255e2b2384c (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit b04fd89cb8bc48bad63fb59c91400bbf70e1f510 Author: Jonathan Wakely <jwakely@redhat.com> Date: Wed Apr 28 18:08:33 2021 +0100 Replace <tt> elements with <code> for HTML5 compatibility diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html index 912fc59b..23f71411 100644 --- a/htdocs/gcc-12/changes.html +++ b/htdocs/gcc-12/changes.html @@ -31,11 +31,12 @@ a work-in-progress.</p> <h2>Caveats</h2> <ul> <li> - Two non-standard <tt>std::pair</tt> constructors have been deprecated. - These allowed the use of an rvalue and a literal <tt>0</tt> to construct - a pair containing a move-only type and a pointer. The <tt>nullptr</tt> - keyword should be used to initialize the pointer member instead of a - literal <tt>0</tt>, as this is portable to other C++ implementations. + Two non-standard <code>std::pair</code> constructors have been deprecated. + These allowed the use of an rvalue and a literal <code>0</code> to + construct a pair containing a move-only type and a pointer. + The <code>nullptr</code> keyword should be used to initialize the pointer + member instead of a literal <code>0</code>, as this is portable to other + C++ implementations. </li> <li>...</li> </ul> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-12/changes.html | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-04-28 17:10 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210428171024.DEFD13AA1407@sourceware.org \ --to=redi@sourceware.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: 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).