From: Sam James <sam@gentoo.org>
To: gcc-patches@gcc.gnu.org
Cc: Sam James <sam@gentoo.org>
Subject: [PATCH 3/4] maintainer-scripts/gcc_release: use HTTPS for links
Date: Thu, 2 Nov 2023 08:39:07 +0000 [thread overview]
Message-ID: <20231102084058.1142941-3-sam@gentoo.org> (raw)
In-Reply-To: <20231102084058.1142941-1-sam@gentoo.org>
maintainer-scripts/
* gcc_release: Use HTTPS for links.
Signed-off-by: Sam James <sam@gentoo.org>
---
maintainer-scripts/gcc_release | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/maintainer-scripts/gcc_release b/maintainer-scripts/gcc_release
index 4cd1fa799660..cf6a5731c609 100755
--- a/maintainer-scripts/gcc_release
+++ b/maintainer-scripts/gcc_release
@@ -25,7 +25,7 @@
#
# You should have received a copy of the GNU General Public License
# along with GCC; see the file COPYING3. If not see
-# <http://www.gnu.org/licenses/>.
+# <https://www.gnu.org/licenses/>.
#
########################################################################
@@ -454,7 +454,7 @@ announce_snapshot() {
echo \
"Snapshot gcc-"${RELEASE}" is now available on
https://gcc.gnu.org/pub/gcc/snapshots/"${RELEASE}"/
-and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
+and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC "${BRANCH}" git branch
with the following options: "git://gcc.gnu.org/git/gcc.git branch ${GITBRANCH} revision ${GITREV}"
@@ -472,7 +472,7 @@ You'll find:
<body>
<h1>GCC "${RELEASE}" Snapshot</h1>
-<p>The <a href =\"http://gcc.gnu.org/\">GCC Project</a> makes
+<p>The <a href =\"https://gcc.gnu.org/\">GCC Project</a> makes
periodic snapshots of the GCC source tree available to the public
for testing purposes.</p>
--
2.42.0
next prev parent reply other threads:[~2023-11-02 8:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 8:39 [PATCH 1/4] contrib: add generate_snapshot_index.py Sam James
2023-11-02 8:39 ` [PATCH 2/4] maintainer-scripts/gcc_release: create index between snapshots <-> commits Sam James
2023-11-02 9:07 ` Jonathan Wakely
2023-11-02 10:18 ` Andreas Schwab
2023-11-02 10:25 ` Jonathan Wakely
2023-11-02 22:18 ` rep.dot.nop
2023-11-02 8:39 ` Sam James [this message]
2023-11-02 18:59 ` [PATCH 3/4] maintainer-scripts/gcc_release: use HTTPS for links Joseph Myers
2023-11-02 8:39 ` [PATCH 4/4] maintainer-scripts/gcc_release: cleanup whitespace Sam James
2023-11-02 19:00 ` Joseph Myers
2023-11-10 23:35 ` Sam James
2023-11-14 0:21 ` Joseph Myers
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=20231102084058.1142941-3-sam@gentoo.org \
--to=sam@gentoo.org \
--cc=gcc-patches@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).