public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Subject: [pushed] wwwdocs: testing: Avoid a duplicate link
Date: Thu, 2 Mar 2023 08:41:31 +0100 (CET)	[thread overview]
Message-ID: <20230302074134.721DE33E59@hamza.pair.com> (raw)

This came up in a conversation with Jan. (We already have a link a bit 
earlier on that page.)

Pushed.

Gerald
---
 htdocs/testing/index.html | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/htdocs/testing/index.html b/htdocs/testing/index.html
index bd6219ab..012ac287 100644
--- a/htdocs/testing/index.html
+++ b/htdocs/testing/index.html
@@ -115,10 +115,8 @@ the testsuite directories.</p>
   <li>Build and test packages that are normally available on your
       platform and for which you have access to source.</li>
   <li>Run benchmarks regularly and report performance regressions.</li>
-  <li>Extend the
-      <a href="http://toolchain.lug-owl.de/buildbot/">build robot</a> to also
-      do local builds, run the testsuite, visualize test result differences
-      and probably use something like
+  <li>Extend the build robot to also do local builds, run the testsuite,
+      visualize test result differences and probably use something like
       <a href="http://buildbot.net/">BuildBot</a>. Some of the
       <a href="https://gcc.gnu.org/wiki/CompileFarm">Compile Farm</a> machines
       could also be used.</li>
-- 
2.39.1

                 reply	other threads:[~2023-03-02  7:41 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=20230302074134.721DE33E59@hamza.pair.com \
    --to=gerald@pfeifer.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jbglaw@lug-owl.de \
    /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).