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. 97dfd479fc922ee33fb25096b99df8492152f750 Date: Fri, 7 Jun 2024 22:15:54 +0000 (GMT) [thread overview] Message-ID: <20240607221554.5D7CD3858D20@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 97dfd479fc922ee33fb25096b99df8492152f750 (commit) from 4260d675af42b9c97e29818ab3b3154d27103d49 (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 97dfd479fc922ee33fb25096b99df8492152f750 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Sat Jun 8 00:15:45 2024 +0200 simtest-howto: Use https to link to our install docs diff --git a/htdocs/simtest-howto.html b/htdocs/simtest-howto.html index d9c027fd..3afbdb0b 100644 --- a/htdocs/simtest-howto.html +++ b/htdocs/simtest-howto.html @@ -115,7 +115,7 @@ cd gcc && find . -print | cpio -pdlmu ../combined && cd .. <h2>Build it</h2> <p>Make sure the - <a href="http://gcc.gnu.org/install/prerequisites.html">building + <a href="https://gcc.gnu.org/install/prerequisites.html">building prerequisites</a> for GCC are met, for example a host GCC no earlier than 3.4 or later, with C++ support enabled.</p> ----------------------------------------------------------------------- Summary of changes: htdocs/simtest-howto.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2024-06-07 22:15 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=20240607221554.5D7CD3858D20@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).