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. 296380e4e087525fcc24bc8ded3f65e4dcf32cdc
Date: Sun, 11 Apr 2021 14:06:10 +0000 (GMT)	[thread overview]
Message-ID: <20210411140610.2B27B38930DD@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  296380e4e087525fcc24bc8ded3f65e4dcf32cdc (commit)
      from  69cb4c5f2ea3534b7ff5e03324692172096b3f56 (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 296380e4e087525fcc24bc8ded3f65e4dcf32cdc
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Sun Apr 11 16:05:52 2021 +0200

    bugs: Remove extraneous </p>.

diff --git a/htdocs/bugs/index.html b/htdocs/bugs/index.html
index 4a258213..80dac392 100644
--- a/htdocs/bugs/index.html
+++ b/htdocs/bugs/index.html
@@ -298,7 +298,7 @@ represent all real numbers exactly, so it has to use
 approximations. When computing with approximation, the computer needs
 to round to the nearest representable number.</p>
 
-<p>This is an inherent limitation of floating point types, not a bug.</p>
+<p>This is an inherent limitation of floating point types, not a bug.
 See Goldberg's <a href="https://www.validlab.com/goldberg/paper.pdf">What
 Every Computer Scientist Should Know about Floating-Point Arithmetic</a>
 for more information.</p></dd>

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

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


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2021-04-11 14:06 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=20210411140610.2B27B38930DD@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).