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. 10f3336548be13ce41931f43b7bc89710c9f1d89
Date: Wed, 22 Nov 2023 23:21:35 +0000 (GMT)	[thread overview]
Message-ID: <20231122232135.A6A2F3858CDA@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  10f3336548be13ce41931f43b7bc89710c9f1d89 (commit)
      from  0d447f9a4b920c8deea04f5aae167ca1b3ee17f0 (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 10f3336548be13ce41931f43b7bc89710c9f1d89
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Thu Nov 23 00:20:37 2023 +0100

    branching: No longer refer to buildstat.html

diff --git a/htdocs/branching.html b/htdocs/branching.html
index 0d48dce1..23ff92e8 100644
--- a/htdocs/branching.html
+++ b/htdocs/branching.html
@@ -52,9 +52,6 @@ populate it with initial copies of <code>changes.html</code> and
 based on the previous release branch to the directory corresponding to
 the newly created release branch.</li>
 	
-<li>Add <code>buildstat.html</code> and update the toplevel
-<code>buildstat.html</code> accordingly.</li>
-
 <li>Update the toplevel <code>index.html</code> page to show the new active
 release branch, the current release series, and active development
 (mainline).  Update the version and development stage for mainline.</li>

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

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


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-11-22 23:21 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=20231122232135.A6A2F3858CDA@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).