public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. d1c6bdebaf26da2ca69538572aa822a12d845c11
Date: Fri, 10 Mar 2023 02:18:56 +0000 (GMT)	[thread overview]
Message-ID: <20230310021856.E83343858C5E@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  d1c6bdebaf26da2ca69538572aa822a12d845c11 (commit)
      from  300a5505eeb55cef873ec486baf5164d9836acec (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 d1c6bdebaf26da2ca69538572aa822a12d845c11
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Fri Mar 10 03:18:46 2023 +0100

    gcc-13: Fix markup

diff --git a/htdocs/gcc-13/porting_to.html b/htdocs/gcc-13/porting_to.html
index 6ac9cb7f..7d14e9e3 100644
--- a/htdocs/gcc-13/porting_to.html
+++ b/htdocs/gcc-13/porting_to.html
@@ -144,7 +144,7 @@ abort with fast excess precision, where whether something is evaluated in
 <code>long double</code> precision depends on what evaluations are
 done in the i387 floating point stack or are spilled from it.</p>
 
-</p>The <code>-fexcess-precision=fast</code> option can be used to
+<p>The <code>-fexcess-precision=fast</code> option can be used to
 request the previous behavior.</p>
 
 <h3 id="alloc-rebind">allocator_traits&lt;A&gt;::rebind_alloc&lt;A::value_type&gt; must be A</h3>

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-13/porting_to.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-03-10  2:18 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=20230310021856.E83343858C5E@sourceware.org \
    --to=gerald@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: 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).