From: Gerald Pfeifer <gerald@pfeifer.com>
To: Thomas Schwinge <thomas@schwinge.name>
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: Fri, 24 Nov 2023 01:01:51 +0100 (CET) [thread overview]
Message-ID: <4b4f8211-d61f-fb6c-aa47-087ea6daab68@pfeifer.com> (raw)
In-Reply-To: <87pm04stn0.fsf@euler.schwinge.homeip.net>
On Mon, 20 Nov 2023, Thomas Schwinge wrote:
>> 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?
The libstdc++ docs refer to gcc-results and I'll see to add this to the
web pages where applicable.
> 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>
I have taken care of all these and will look into gcc/doc/install.texi in
the coming days.
Thanks for bringing this up!
Gerald
prev parent reply other threads:[~2023-11-24 0:01 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
2023-11-20 14:12 ` Jonathan Wakely
2023-11-24 0:01 ` Gerald Pfeifer [this message]
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=4b4f8211-d61f-fb6c-aa47-087ea6daab68@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libstdc++@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=thomas@schwinge.name \
/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).