[gimp-web/testing: 1/2] Fix https://gitlab.gnome.org/Infrastructure/gimp-web/issues/133

[Pat David <patdavid src gnome org>]

commit a4aad3547b88497a8f828a98a11ab96d1ac34c7b
Author: nmat <15926-nmat users noreply gitlab gnome org>
Date:   Sat May 11 23:08:56 2019 +0200

    Fix https://gitlab.gnome.org/Infrastructure/gimp-web/issues/133

 content/source/howtos/gimp-git-build.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/content/source/howtos/gimp-git-build.md b/content/source/howtos/gimp-git-build.md
index b8b34264..5509b1bd 100644
--- a/content/source/howtos/gimp-git-build.md
+++ b/content/source/howtos/gimp-git-build.md
@@ -23,7 +23,7 @@ Making use of config.site nullifies the need to manually manage environment vari
 
 Then, assuming you have all the dependencies, you build GIMP the first time with:
 
-    git clone git://git.gnome.org/gimp
+    git clone https://gitlab.gnome.org/GNOME/gimp.git
     cd gimp
     ./autogen.sh --prefix=$PREFIX
     make
@@ -41,6 +41,6 @@ Note that the latter works without requiring any environment variables to be set
 The above approach works for as good as all GNOME projects, including GLib, babl, GEGL and GTK+. This makes 
it easy to adapt to GIMP's build requirements of these and other libraries even if your distro doesn't meet 
them. Let me know if you have problems!
 
 <small>
-Originally published at:  
+Originally published at:
 
[http://www.chromecode.com/2009/12/best-way-to-keep-up-with-gimp-from-git_26.html](http://www.chromecode.com/2009/12/best-way-to-keep-up-with-gimp-from-git_26.html)
 </small>