maint: prefer https: to git:

The idea is to defend against some adversary-in-the-middle attacks.

diff --git a/.gitmodules b/.gitmodules
index bb9e1baf5180abe9d8467d45bd79707f2444f332..9993f552737a95651e6fb08ea74c4020514cb400 100644 (file)
--- a/.gitmodules
+++ b/.gitmodules
@@ -1,3 +1,3 @@
 [submodule "gnulib"]
         path = gnulib
-        url = git://git.sv.gnu.org/gnulib.git
+        url = https://git.savannah.gnu.org/git/gnulib.git

diff --git a/HACKING b/HACKING
index 997dd90dfadcf57bccf31a4ce3ed2309fa20aa9d..11f3967ecd048580f5dfb99bac0db5097a2429a3 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -20,7 +20,7 @@ Use the latest upstream sources
 Base any changes you make on the latest upstream sources.
 You can get a copy of the latest with this command:
 
-    git clone git://git.sv.gnu.org/coreutils
+    git clone https://git.savannah.gnu.org/git/coreutils.git
     cd coreutils
 
 That downloads the entire repository, including revision control history
@@ -95,7 +95,7 @@ Make your changes on a private "topic" branch
 =============================================
 So you checked out coreutils like this:
 
-  git clone git://git.sv.gnu.org/coreutils
+  git clone https://git.savannah.gnu.org/git/coreutils.git
 
 Now, cd into the coreutils/ directory and run:
 

diff --git a/README-hacking b/README-hacking
index bc484638d53adfb5c7f288bc1dc080ebdcddbed5..bd54844a2b5a1e581115f160bd31d777aa91f6d0 100644 (file)
--- a/README-hacking
+++ b/README-hacking
@@ -27,7 +27,7 @@ few prerequisites, later, a plain 'git pull && make' typically suffices.
 
 You can get a copy of the source repository like this:
 
-        $ git clone git://git.sv.gnu.org/<packagename>
+        $ git clone https://git.savannah.gnu.org/git/<packagename>
         $ cd <packagename>
 
 where '<packagename>' stands for 'coreutils' or whatever other package