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. 8d814b957e6d29320b46d37116274f0b493d3793
Date: Mon, 13 Mar 2023 18:43:17 +0000 (GMT)	[thread overview]
Message-ID: <20230313184317.65F153858D1E@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  8d814b957e6d29320b46d37116274f0b493d3793 (commit)
      from  303c5592f31a73cc90e2a799fe0455873db512b2 (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 8d814b957e6d29320b46d37116274f0b493d3793
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Mon Mar 13 19:42:21 2023 +0100

    style: Add a link to our testing page

diff --git a/htdocs/style.mhtml b/htdocs/style.mhtml
index 1b778151..dcc27cc4 100644
--- a/htdocs/style.mhtml
+++ b/htdocs/style.mhtml
@@ -121,6 +121,7 @@
   <a href="<get-var BACKPATH>frontends.html">Front ends</a><br>
   <a href="<get-var BACKPATH>backends.html">Back ends</a><br>
   <a href="<get-var BACKPATH>extensions.html">Extensions</a><br>
+  <a href="<get-var BACKPATH>testing/">Testing</a><br>
   <a href="<get-var BACKPATH>benchmarks/">Benchmarks</a><br>
   <a href="<get-var BACKPATH>translation.html">Translations</a><br>
   </td></tr>

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

Summary of changes:
 htdocs/style.mhtml | 1 +
 1 file changed, 1 insertion(+)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-03-13 18:43 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=20230313184317.65F153858D1E@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).