public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Subject: [committed] wwwdocs: testing: Switch www.netlib.org to https
Date: Sat, 29 Oct 2022 23:18:17 +0200 (CEST)	[thread overview]
Message-ID: <20221029211820.18BD833E4D@hamza.pair.com> (raw)

Not sure anyone is (still) using these instructions?

Still, as long as we have them, adjust the links.

Pushed.
Gerald

---
 htdocs/testing/testing-lapack.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/htdocs/testing/testing-lapack.html b/htdocs/testing/testing-lapack.html
index a819b7d5..6416ac3e 100644
--- a/htdocs/testing/testing-lapack.html
+++ b/htdocs/testing/testing-lapack.html
@@ -11,14 +11,14 @@
 <h1>LAPACK build and test guide</h1>
 
 <p>This page is a guide to building the
-<a href="http://www.netlib.org/lapack/index.html">LAPACK</a> linear
+<a href="https://www.netlib.org/lapack/index.html">LAPACK</a> linear
 algebra package and running its testing and timing programs as part of
 GCC integration testing.</p>
 
 <h2>Resource usage</h2>
 
 <p>The LAPACK distribution, available from the netlib repository at
-<a href="http://www.netlib.org/lapack/lapack.tgz">lapack.tgz</a>,
+<a href="https://www.netlib.org/lapack/lapack.tgz">lapack.tgz</a>,
 is a 5 MB file.  The uncompressed LAPACK distribution comprises some 35 MB
 of source files.  Building the libraries, test and timing programs adds
 between 80 and 100 MB of objects, libraries and executables to this.</p>
-- 
2.38.0

                 reply	other threads:[~2022-10-29 21: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=20221029211820.18BD833E4D@hamza.pair.com \
    --to=gerald@pfeifer.com \
    --cc=gcc-patches@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).