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. 8a551dfcd1b64e7970b43c0a034972167564e062
Date: Sat, 11 Mar 2023 23:08:23 +0000 (GMT)	[thread overview]
Message-ID: <20230311230823.BE0473858D1E@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  8a551dfcd1b64e7970b43c0a034972167564e062 (commit)
      from  a328847507b0a3e0d6a3361bbef57d769e0fb45f (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 8a551dfcd1b64e7970b43c0a034972167564e062
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Sun Mar 12 00:05:17 2023 +0100

    testing: Further adjust link to upstream FTensor

diff --git a/htdocs/testing/testing-ftensor.html b/htdocs/testing/testing-ftensor.html
index 7b1f4675..1f9de177 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="https://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-03-11 23:08 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=20230311230823.BE0473858D1E@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).