public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: gerald@gcc.gnu.org To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. da0ef87da0ed79d4315af901f3ae68889d9c32cc Date: Tue, 21 Jan 2020 06:52:00 -0000 [thread overview] Message-ID: <20200121065230.109232.qmail@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 da0ef87da0ed79d4315af901f3ae68889d9c32cc (commit) from b34fe1eb529b823686a99964199d978e2f25dcc0 (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 da0ef87da0ed79d4315af901f3ae68889d9c32cc Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Tue Jan 21 07:52:03 2020 +0100 Switch over www.gnu.org to https. diff --git a/htdocs/fortran/index.html b/htdocs/fortran/index.html index b7a71de2..1d140b3a 100644 --- a/htdocs/fortran/index.html +++ b/htdocs/fortran/index.html @@ -14,7 +14,7 @@ <p>The purpose of the GNU Fortran (GFortran) project is to develop the Fortran compiler front end and run-time libraries for GCC, the GNU Compiler Collection. GFortran development is part -of the <a href="http://www.gnu.org/">GNU Project</a>. We seek to bring +of the <a href="https://www.gnu.org">GNU Project</a>. We seek to bring free number crunching to a broad spectrum of platforms and users.</p> <p>In particular, the project wishes to reach users of the ----------------------------------------------------------------------- Summary of changes: htdocs/fortran/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-01-21 6:52 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=20200121065230.109232.qmail@sourceware.org \ --to=gerald@gcc.gnu.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).