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. b74309c36e59105ef0d8e0d91a85a5bfa884e175 Date: Fri, 17 Feb 2023 01:22:33 +0000 (GMT) [thread overview] Message-ID: <20230217012233.289FF385B53E@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 b74309c36e59105ef0d8e0d91a85a5bfa884e175 (commit) from 0226fd8acf09e35181fdf50e386b0afda66f832f (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 b74309c36e59105ef0d8e0d91a85a5bfa884e175 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Fri Feb 17 02:19:19 2023 +0100 Tweak the link to upstream FTensor. diff --git a/htdocs/testing/testing-ftensor.html b/htdocs/testing/testing-ftensor.html index 2e67b4d8..7b1f4675 100644 --- a/htdocs/testing/testing-ftensor.html +++ b/htdocs/testing/testing-ftensor.html @@ -11,7 +11,7 @@ <h1>FTensor build and test guide</h1> <p>This page is a guide to running the testing and timing programs for the -<a href="http://www.wlandry.net/Projects/FTensor">FTensor</a> +<a href="https://wlandry.net/Projects/FTensor">FTensor</a> tensor class library as part of GCC integration testing.</p> <h2>Resource usage</h2> ----------------------------------------------------------------------- Summary of changes: htdocs/testing/testing-ftensor.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-02-17 1:22 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=20230217012233.289FF385B53E@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: 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).