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. 4b43815f8db97d1b99e245779a059ddcca0433bd
Date: Mon, 24 Aug 2020 16:53:14 +0000 (GMT)	[thread overview]
Message-ID: <20200824165314.B97D33857C53@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  4b43815f8db97d1b99e245779a059ddcca0433bd (commit)
      from  8d046142a4e6779b3c4ab20903f2ca765597a2fc (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 4b43815f8db97d1b99e245779a059ddcca0433bd
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Mon Aug 24 18:52:42 2020 +0200

    Switch www.validlab.com to https

diff --git a/htdocs/bugs/index.html b/htdocs/bugs/index.html
index a6631d8a..88fba1b9 100644
--- a/htdocs/bugs/index.html
+++ b/htdocs/bugs/index.html
@@ -300,7 +300,7 @@ to round to the nearest representable number.</p>
 
 <p>This is not a bug in the compiler, but an inherent limitation of
 the floating point types. Please study
-<a href="http://www.validlab.com/goldberg/paper.ps">this paper</a>
+<a href="https://www.validlab.com/goldberg/paper.ps">this paper</a>
 for more information.</p></dd>
 </dl>
 

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

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


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-08-24 16:53 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=20200824165314.B97D33857C53@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).