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. f0c8bde69088221c17cb5e84ae628254883602cb
Date: Wed, 22 Nov 2023 23:24:06 +0000 (GMT)	[thread overview]
Message-ID: <20231122232406.2B4B23893655@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  f0c8bde69088221c17cb5e84ae628254883602cb (commit)
      from  10f3336548be13ce41931f43b7bc89710c9f1d89 (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 f0c8bde69088221c17cb5e84ae628254883602cb
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Thu Nov 23 00:22:44 2023 +0100

    releasing: No longer refer to buildstat.html

diff --git a/htdocs/releasing.html b/htdocs/releasing.html
index 1cd56f72..c7365e64 100644
--- a/htdocs/releasing.html
+++ b/htdocs/releasing.html
@@ -85,9 +85,6 @@ web pages.</li>
 <li>Update the version numbers of the current and future releases on
 the main web page, and add a proper news item there as well.</li>
 
-<li>For a new major release, ensure that the build status page is present
-and add a link from the main <code>buildstat.html</code> page.</li>
-
 <li>Generate online documentation for the new release with
 <code>update_web_docs_git</code>.  The appropriate command to run (as gccadmin)
 to generate the documentation would be <code>scripts/update_web_docs_git

-----------------------------------------------------------------------

Summary of changes:
 htdocs/releasing.html | 3 ---
 1 file changed, 3 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-11-22 23:24 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=20231122232406.2B4B23893655@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: 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).