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. 186d8eefd7ff819fb15990c367c5cd43150e601d Date: Sat, 22 Jun 2024 12:52:26 +0000 (GMT) [thread overview] Message-ID: <20240622125226.B6EA0385DDCC@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 186d8eefd7ff819fb15990c367c5cd43150e601d (commit) from 3da227050417c1032e5057626d6ccd2bef7282b3 (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 186d8eefd7ff819fb15990c367c5cd43150e601d Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Sat Jun 22 14:52:06 2024 +0200 news: Tweak MPFR link diff --git a/htdocs/news.html b/htdocs/news.html index 471b31b7..e78abfc3 100644 --- a/htdocs/news.html +++ b/htdocs/news.html @@ -798,7 +798,7 @@ annual report for 2008</a></dd> <dt>January 6, 2007</dt> <dd>Kaveh Ghazi has integrated the GCC middle-end with the <a - href="http://www.mpfr.org/">MPFR</a> library, allowing more + href="https://www.mpfr.org">MPFR</a> library, allowing more effective <a href="gcc-4.3/changes.html#mpfropts">compile-time optimizations</a>. As a result, this library and the <a href="https://gmplib.org/">GMP</a> library are now <a ----------------------------------------------------------------------- Summary of changes: htdocs/news.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2024-06-22 12: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=20240622125226.B6EA0385DDCC@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).