From: Thomas Schwinge <thomas@schwinge.name>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Richard Biener <richard.guenther@gmail.com>,
gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [pushed] wwwdocs: *: Remove unused buildstat pages
Date: Mon, 20 Nov 2023 09:42:27 +0100 [thread overview]
Message-ID: <87pm04stn0.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <20231015214241.B37BB33EB9@hamza.pair.com>
Hi!
On 2023-10-15T23:42:39+0200, Gerald Pfeifer <gerald@pfeifer.com> wrote:
> [ Release managers, heads-up for when you branch future releases! ]
> For GCC 9 to GCC 13 the per-release series buildstat pages have not
> been populated at all, so remove them and reference from the respective
> main release pages.
ACK; I had recently run into such an empty page, and wanted to suggest
the same.
We still need to update the docs some more. Do we just remove all
references (and related text), and/or refer to the gcc-testresults
mailing list?
In wwwdocs:
htdocs/branching.html:<li>Add <code>buildstat.html</code> and update the toplevel
htdocs/branching.html:<code>buildstat.html</code> accordingly.</li>
htdocs/faq.html:Reports of <a href="buildstat.html">successful builds</a>
htdocs/faq.html-for several versions of GCC are also available at the web site.</p>
htdocs/releasing.html-<li>For a new major release, ensure that the build status page is present
htdocs/releasing.html:and add a link from the main <code>buildstat.html</code> page.</li>
In GCC:
gcc/doc/install.texi-Lists of successful builds for released versions of GCC are
gcc/doc/install.texi:available at @uref{https://gcc.gnu.org/buildstat.html}.
gcc/doc/install.texi-These lists are updated as new information becomes available.
gcc/doc/install.texi-Some of these archived results are linked from the build status lists
gcc/doc/install.texi:at @uref{https://gcc.gnu.org/buildstat.html}, although not everyone who
gcc/doc/install.texi-reports a successful build runs the testsuites and submits the results.
gcc/doc/install.texi-If you are bootstrapping a released version of GCC then please
gcc/doc/install.texi-quickly review the build status page for your release, available from
gcc/doc/install.texi:@uref{https://gcc.gnu.org/buildstat.html}.
libstdc++-v3/doc/xml/faq.xml- the rapid development and near-legendary
libstdc++-v3/doc/xml/faq.xml: <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/buildstat.html">portability</link>
libstdc++-v3/doc/xml/faq.xml- that are the hallmarks of an open-source project are applied to libstdc++.
libstdc++-v3/doc/xml/manual/test.xml- Archives of test results for various versions and platforms are
libstdc++-v3/doc/xml/manual/test.xml: available on the GCC website in the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://gcc.gnu.org/gcc-4.3/buildstat.html">build
libstdc++-v3/doc/xml/manual/test.xml- status</link> section of each individual release, and are also
libstdc++-v3/doc/xml/manual/test.xml- archived on a daily basis on the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://gcc.gnu.org/ml/gcc-testresults/current">gcc-testresults</link>
Grüße
Thomas
> htdocs/gcc-10/buildstat.html | 27 ---------------------------
> htdocs/gcc-10/index.html | 3 ---
> htdocs/gcc-11/buildstat.html | 27 ---------------------------
> htdocs/gcc-11/index.html | 3 ---
> htdocs/gcc-12/buildstat.html | 27 ---------------------------
> htdocs/gcc-12/index.html | 3 ---
> htdocs/gcc-13/buildstat.html | 27 ---------------------------
> htdocs/gcc-13/index.html | 3 ---
> htdocs/gcc-9/buildstat.html | 27 ---------------------------
> htdocs/gcc-9/index.html | 3 ---
> 10 files changed, 150 deletions(-)
> delete mode 100644 htdocs/gcc-10/buildstat.html
> delete mode 100644 htdocs/gcc-11/buildstat.html
> delete mode 100644 htdocs/gcc-12/buildstat.html
> delete mode 100644 htdocs/gcc-13/buildstat.html
> delete mode 100644 htdocs/gcc-9/buildstat.html
next prev parent reply other threads:[~2023-11-20 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-15 21:42 Gerald Pfeifer
2023-11-20 8:42 ` Thomas Schwinge [this message]
2023-11-20 14:12 ` Jonathan Wakely
2023-11-24 0:01 ` Gerald Pfeifer
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=87pm04stn0.fsf@euler.schwinge.homeip.net \
--to=thomas@schwinge.name \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libstdc++@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
/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: link
Be 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).