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. 15015b926775d14450112e2938ce6177940813a9 Date: Wed, 1 Apr 2020 07:25:38 +0000 (GMT) [thread overview] Message-ID: <20200401072538.D578E385BF83@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 15015b926775d14450112e2938ce6177940813a9 (commit) from 0e76160551501374248cfd40b1afb6ae2df5025f (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 15015b926775d14450112e2938ce6177940813a9 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Wed Apr 1 09:25:21 2020 +0200 Move pspace.org to https. diff --git a/htdocs/readings.html b/htdocs/readings.html index 40ad4d62..84fc0404 100644 --- a/htdocs/readings.html +++ b/htdocs/readings.html @@ -27,7 +27,7 @@ <li><a href="https://en.wikibooks.org/wiki/GNU_C_Compiler_Internals">GNU C Compiler Internals (Wikibook)</a>, numerous contributors.</li> - <li><a href="http://www.pspace.org/a/thesis/">Compilation + <li><a href="https://www.pspace.org/a/thesis/">Compilation of Functional Programming Languages using GCC -- Tail Calls</a> by Andreas Bauer.</li> <!-- ----------------------------------------------------------------------- Summary of changes: htdocs/readings.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-04-01 7:25 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=20200401072538.D578E385BF83@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).