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. d3f86b59e343ab10078a84aa927f760779b2d5d3 Date: Thu, 23 Nov 2023 00:46:09 +0000 (GMT) [thread overview] Message-ID: <20231123004609.B62DC3857B81@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 d3f86b59e343ab10078a84aa927f760779b2d5d3 (commit) from f0c8bde69088221c17cb5e84ae628254883602cb (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 d3f86b59e343ab10078a84aa927f760779b2d5d3 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Thu Nov 23 01:45:19 2023 +0100 faq: Refer to gcc-testresults instead of buildstat.html diff --git a/htdocs/faq.html b/htdocs/faq.html index 203661dc..5c713a70 100644 --- a/htdocs/faq.html +++ b/htdocs/faq.html @@ -99,8 +99,9 @@ about known problems with installing or using GCC on particular platforms. These are included in the sources for a release in INSTALL/specific.html, and the <a href="https://gcc.gnu.org/install/specific.html">latest version</a> is always available at the GCC web site. -Reports of <a href="buildstat.html">successful builds</a> -for several versions of GCC are also available at the web site.</p> +There you also find +<a href="https://gcc.gnu.org/pipermail/gcc-testresults/">reports around +successful builds</a>.</p> <hr> <h1 id="installation">Installation</h1> ----------------------------------------------------------------------- Summary of changes: htdocs/faq.html | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-11-23 0:46 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=20231123004609.B62DC3857B81@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).