From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Subject: [PATCH htdocs] download: fix more http:// -> https://
Date: Thu, 12 Jan 2023 00:24:46 -0500 [thread overview]
Message-ID: <20230112052446.13680-1-vapier@gentoo.org> (raw)
---
download/index.html | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/download/index.html b/download/index.html
index aef60cc80666..ffbb88e6af2a 100644
--- a/download/index.html
+++ b/download/index.html
@@ -54,15 +54,15 @@ You can download the most recent official release of GDB from either
Project GNU's FTP server, or Red Hat's sources site:
<pre>
-<a href="https://ftp.gnu.org/gnu/gdb" >http://ftp.gnu.org/gnu/gdb</a> (<a href="http://www.gnu.org/order/ftp.html">mirrors</a>)
-<a href="ftp://sourceware.org/pub/gdb/releases/" >ftp://sourceware.org/pub/gdb/releases/</a> (<a href="https://sourceware.org/mirrors.html">mirrors</a>).
+<a href="https://ftp.gnu.org/gnu/gdb">https://ftp.gnu.org/gnu/gdb</a> (<a href="https://www.gnu.org/order/ftp.html">mirrors</a>)
+<a href="ftp://sourceware.org/pub/gdb/releases/">ftp://sourceware.org/pub/gdb/releases/</a> (<a href="https://sourceware.org/mirrors.html">mirrors</a>)
</pre>
As with all GNU projects, you can verify the signatures for gnu project
files with the keyring file from:
<pre>
-<a href="ftp://ftp.gnu.org/gnu/gnu-keyring.gpg">ftp://ftp.gnu.org/gnu/gnu-keyring.gpg</a> (see <a href="https://ftp.gnu.org/README">http://ftp.gnu.org/README</a> for more info).
+<a href="ftp://ftp.gnu.org/gnu/gnu-keyring.gpg">ftp://ftp.gnu.org/gnu/gnu-keyring.gpg</a> (see <a href="https://ftp.gnu.org/README">https://ftp.gnu.org/README</a> for more info).
</pre>
Sources to the current development version are also available using
--
2.39.0
reply other threads:[~2023-01-12 5:24 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=20230112052446.13680-1-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.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).