public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r11-6345] libstdc++: Move Valgrind references to https
Date: Sun, 27 Dec 2020 10:17:41 +0000 (GMT)	[thread overview]
Message-ID: <20201227101741.F263E386EC72@sourceware.org> (raw)

https://gcc.gnu.org/g:0e283e2c9f15d8abfd6a57c05d0845f8c4e08827

commit r11-6345-g0e283e2c9f15d8abfd6a57c05d0845f8c4e08827
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Sun Dec 27 11:16:21 2020 +0100

    libstdc++: Move Valgrind references to https
    
    libstdc++-v3:
    
    2020-12-27  Gerald Pfeifer  <gerald@pfeifer.com>
    
            * doc/xml/manual/debug.xml: Move Valgrind references to https.
            * doc/html/manual/debug.html: Regenerate.

Diff:
---
 libstdc++-v3/doc/html/manual/debug.html | 4 ++--
 libstdc++-v3/doc/xml/manual/debug.xml   | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/libstdc++-v3/doc/html/manual/debug.html b/libstdc++-v3/doc/html/manual/debug.html
index d85685dce9c..a4e31f81d43 100644
--- a/libstdc++-v3/doc/html/manual/debug.html
+++ b/libstdc++-v3/doc/html/manual/debug.html
@@ -167,9 +167,9 @@
 </p><p>
   The approach described above is known to work with the following race
   detection tools:
-  <a class="link" href="http://valgrind.org/docs/manual/drd-manual.html" target="_top">
+  <a class="link" href="https://valgrind.org/docs/manual/drd-manual.html" target="_top">
   DRD</a>,
-  <a class="link" href="http://valgrind.org/docs/manual/hg-manual.html" target="_top">
+  <a class="link" href="https://valgrind.org/docs/manual/hg-manual.html" target="_top">
   Helgrind</a>, and
   <a class="link" href="https://github.com/google/sanitizers" target="_top">
   ThreadSanitizer</a> (this refers to ThreadSanitizer v1, not the
diff --git a/libstdc++-v3/doc/xml/manual/debug.xml b/libstdc++-v3/doc/xml/manual/debug.xml
index 7b60b497cfc..1fedf0acca1 100644
--- a/libstdc++-v3/doc/xml/manual/debug.xml
+++ b/libstdc++-v3/doc/xml/manual/debug.xml
@@ -245,10 +245,10 @@
   The approach described above is known to work with the following race
   detection tools:
   <link xmlns:xlink="http://www.w3.org/1999/xlink"
-  xlink:href="http://valgrind.org/docs/manual/drd-manual.html">
+  xlink:href="https://valgrind.org/docs/manual/drd-manual.html">
   DRD</link>,
   <link xmlns:xlink="http://www.w3.org/1999/xlink"
-  xlink:href="http://valgrind.org/docs/manual/hg-manual.html">
+  xlink:href="https://valgrind.org/docs/manual/hg-manual.html">
   Helgrind</link>, and
   <link xmlns:xlink="http://www.w3.org/1999/xlink"
   xlink:href="https://github.com/google/sanitizers">


                 reply	other threads:[~2020-12-27 10:17 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=20201227101741.F263E386EC72@sourceware.org \
    --to=gerald@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@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).