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. 5b9a2f102647fd26ac63f483e1d54377f956ce7e Date: Sun, 30 Jul 2023 22:37:21 +0000 (GMT) [thread overview] Message-ID: <20230730223721.8DE743858D35@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 5b9a2f102647fd26ac63f483e1d54377f956ce7e (commit) from babaaf480b91e13519d5f87977f467ac439a2882 (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 5b9a2f102647fd26ac63f483e1d54377f956ce7e Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Mon Jul 31 00:36:56 2023 +0200 gcc-4.5: Update link to GNU MPC diff --git a/htdocs/gcc-4.5/changes.html b/htdocs/gcc-4.5/changes.html index 2e8f56a7..3d645bb3 100644 --- a/htdocs/gcc-4.5/changes.html +++ b/htdocs/gcc-4.5/changes.html @@ -18,7 +18,7 @@ <ul> <li id="mpccaveat">GCC now requires the <a - href="https://www.multiprecision.org/mpc/">MPC</a> library in order to + href="https://www.multiprecision.org">MPC</a> library in order to build. See the <a href="https://gcc.gnu.org/install/prerequisites.html">prerequisites page</a> for version requirements.</li> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-4.5/changes.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-07-30 22:37 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=20230730223721.8DE743858D35@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).