public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Martin Liska <marxin@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. ba9f8b0cdc23933cf9746518b784775130e2f4e7
Date: Thu, 20 Oct 2022 16:07:52 +0000 (GMT)	[thread overview]
Message-ID: <20221020160752.DE6A8384D19D@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  ba9f8b0cdc23933cf9746518b784775130e2f4e7 (commit)
      from  e9164572d233645b51ed8fa27729a52a0e242984 (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 ba9f8b0cdc23933cf9746518b784775130e2f4e7
Author: Martin Liska <mliska@suse.cz>
Date:   Thu Oct 20 18:05:58 2022 +0200

    Remove dead link to Buildbot.

diff --git a/htdocs/style.mhtml b/htdocs/style.mhtml
index 0790a972..08def35e 100644
--- a/htdocs/style.mhtml
+++ b/htdocs/style.mhtml
@@ -126,7 +126,6 @@
   <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>benchmarks/">Benchmarks</a><br>
-  <a href="http://toolchain.lug-owl.de/buildbot/">Buildbot</a><br>
   <a href="<get-var BACKPATH>translation.html">Translations</a><br>
   </td></tr>
   </table></td></tr>

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

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


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2022-10-20 16:07 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=20221020160752.DE6A8384D19D@sourceware.org \
    --to=marxin@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).