summaryrefslogtreecommitdiff
path: root/README-hacking
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2017-09-19 10:24:05 -0700
committerPaul Eggert <eggert@cs.ucla.edu>2017-09-19 10:43:52 -0700
commitd49274f4ed038cfb361d634dc78143759ffc7a0d (patch)
treee4ec54801c173a68c6f50390d5f9f39d73acb999 /README-hacking
parentfba1018bd31a329096155da48b75f8c9bcdbbd67 (diff)
downloadgzip-d49274f4ed038cfb361d634dc78143759ffc7a0d.tar.gz
maint: prefer HTTPS to HTTP, FTP in URLs
Diffstat (limited to 'README-hacking')
-rw-r--r--README-hacking8
1 files changed, 4 insertions, 4 deletions
diff --git a/README-hacking b/README-hacking
index 3650ff2..4f2279f 100644
--- a/README-hacking
+++ b/README-hacking
@@ -9,10 +9,10 @@ Only the sources are installed in the CVS repository (to ease the
maintenance, merges etc.), therefore you will have to get the latest
stable versions of the maintainer tools we depend upon, including:
-- Automake <http://www.gnu.org/software/automake/>
-- Autoconf <http://www.gnu.org/software/autoconf/>
-- Tar <http://www.gnu.org/software/tar/>
-- Wget <http://www.gnu.org/software/wget/>
+- Automake <https://www.gnu.org/software/automake/>
+- Autoconf <https://www.gnu.org/software/autoconf/>
+- Tar <https://www.gnu.org/software/tar/>
+- Wget <https://www.gnu.org/software/wget/>
Valgrind <http://valgrind.org/> is also highly recommended, if
Valgrind supports your architecture.