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. 928115ec22e3d8eb5128f154465425b04a98aa31 Date: Wed, 1 Feb 2023 09:55:31 +0000 (GMT) [thread overview] Message-ID: <20230201095531.D8C193857C43@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 928115ec22e3d8eb5128f154465425b04a98aa31 (commit) from 83d21fa2e9e6b37cb92dd8e9b840fb8dd9c0ba4b (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 928115ec22e3d8eb5128f154465425b04a98aa31 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Wed Feb 1 10:54:20 2023 +0100 readings: Remove Herman D. Knoble's Fortran Resources The original page is gone, and search engines did not reveal a new location. diff --git a/htdocs/readings.html b/htdocs/readings.html index 0a978e8f..6e640af1 100644 --- a/htdocs/readings.html +++ b/htdocs/readings.html @@ -463,11 +463,6 @@ names. Michel Olagnon's Fortran 90 List</a> contains a "Tests and Benchmarks" section mentioning commercial testsuites. </li> - <li> - <a href="http://www.personal.psu.edu/faculty/h/d/hdk/fortran.html">Herman - D. Knoble's Fortran Resources</a> contain some sections on compiler - validation and benchmarking. - </li> <li> <cite>Complying with Fortran 90, How does the current crop of Fortran 90 compilers measure up to the standard?</cite>, Steven ----------------------------------------------------------------------- Summary of changes: htdocs/readings.html | 5 ----- 1 file changed, 5 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-02-01 9:55 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=20230201095531.D8C193857C43@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).