docs: point to GitLab as the primary git hosting

We still point to git repositories hosted on libvirt.org in various
places. Replace the links to their gitlab.com equivalents.

Note that GitLab is trying to be smart here and
  https://gitlab.com/libvirt/libvirt
redirects to
  https://gitlab.com/libvirt/libvirt.git
when doing a 'git clone' and vice-versa when visiting from the
browser, so I only kept the .git suffix in places that explicitly
mentioned 'git clone'.
Signed-off-by: NJán Tomko <jtomko@redhat.com>
Reviewed-by: NDaniel P. Berrangé <berrange@redhat.com>

ChangeLog

@@ -7,9 +7,9 @@ archives.
 If you're interested in the full list of changes made to libvirt since
 the project was started, you can clone the git repository from
 
-  https://libvirt.org/git/libvirt.git
+  https://gitlab.com/libvirt/libvirt/
 
 and browse them locally using your favorite git history viewer or,
 alternatively, browse them online at
 
-  https://libvirt.org/git/?p=libvirt.git;a=log
+  https://gitlab.com/libvirt/libvirt/-/commits/master

docs/aclpolkit.html.in

@@ -459,7 +459,7 @@ polkit.addRule(function(action, subject) {
 
     <p>
     See
-    <a href="https://libvirt.org/git/?p=libvirt.git;a=tree;f=examples/polkit;hb=HEAD">source code</a>
+    <a href="https://gitlab.com/libvirt/libvirt/-/tree/master/examples/polkit">source code</a>
     for a more complex example.
     </p>
 

docs/bindings.html.in

@@ -49,7 +49,7 @@
       <li>
         <p>
           <strong>Python</strong>: Libvirt's python bindings are split to a
-          separate <a href="https://libvirt.org/git/?p=libvirt-python.git">package</a>
+          separate <a href="https://gitlab.com/libvirt/libvirt-python">package</a>
           since version 1.2.0, older versions came with direct support for the
           Python language.
         </p>

docs/csharp.html.in

@@ -33,19 +33,11 @@
     <p>
       The C# bindings source code is maintained in a <a
       href="http://git-scm.com/">git</a> repository available on
-      <a href="https://libvirt.org/git/">libvirt.org</a>:
+      <a href="https://gitlab.com/libvirt/libvirt-csharp">gitlab.com</a>:
     </p>
 
 <pre>
-git clone https://libvirt.org/git/libvirt-csharp.git
-</pre>
-
-    <p>
-      They can also be browsed online:
-    </p>
-
-<pre>
-<a href="https://libvirt.org/git/?p=libvirt-csharp.git;a=summary">https://libvirt.org/git/?p=libvirt-csharp.git;a=summary</a>
+git clone https://gitlab.com/libvirt/libvirt-csharp.git
 </pre>
 
     <h2><a id="usage">Usage</a></h2>

docs/dbus.html.in

@@ -17,19 +17,11 @@
     <p>
       The D-Bus bindings source code is maintained in a
       <a href="https://git-scm.com/">git</a> repository available on
-      <a href="https://libvirt.org/git/">libvirt.org</a>:
+      <a href="https://gitlab.com/libvirt/libvirt-dbus">gitlab.com</a>:
     </p>
 
 <pre>
-git clone https://libvirt.org/git/libvirt-dbus.git
-</pre>
-
-    <p>
-      They can also be browsed online:
-    </p>
-
-<pre>
-<a href="https://libvirt.org/git/?p=libvirt-dbus.git">https://libvirt.org/git/?p=libvirt-dbus.git</a>
+git clone https://gitlab.com/libvirt/libvirt-dbus.git
 </pre>
 
     <h2><a id="usage">Usage</a></h2>

docs/hacking.rst

@@ -9,9 +9,9 @@ Repositories and external resources
 ===================================
 
 The official upstream repository is kept in git
-(``https://libvirt.org/git/libvirt.git``) and is browsable
+(``https://gitlab.com/libvirt/libvirt``) and is browsable
 along with other libvirt-related repositories (e.g.
-libvirt-python) `online <https://libvirt.org/git/>`__.
+libvirt-python) `online <https://gitlab.com/libvirt>`__.
 
 Patches to translations are maintained via the `zanata
 project <https://fedora.zanata.org/>`__. If you want to fix a

docs/java.html.in

@@ -26,19 +26,11 @@ which you can use to include this in your maven projects.</p>
 <h2>GIT source repository</h2>
 <p> The Java bindings code source is now maintained in a <a
 href="http://git-scm.com/">git</a> repository available on
-<a href="https://libvirt.org/git/">libvirt.org</a>:
+<a href="https://gitlab.com/libvirt/libvirt-java/">gitlab.com</a>:
 </p>
 <pre>
-git clone https://libvirt.org/git/libvirt-java.git
+git clone https://gitlab.com/libvirt/libvirt-java.git
 </pre>
-<p>
-It can also be browsed at
-</p>
-<pre>
-
-<a href="https://libvirt.org/git/?p=libvirt-java.git;a=summary">https://libvirt.org/git/?p=libvirt-java.git;a=summary</a>
-</pre>
-
 
 <h2>Building</h2>
 <p>The code is built using ant, and assumes that you have the jna jar installed. Once you have downloaded

docs/php.html.in

@@ -11,16 +11,10 @@
 <h2>Getting the source</h2>
 <p> The PHP bindings code source is now maintained in a <a
 href="http://git-scm.com/">git</a> repository available on
-<a href="https://libvirt.org/git/">libvirt.org</a>:
+<a href="https://gitlab.com/libvirt/libvirt-php">gitlab.com</a>:
 </p>
 <pre>
-git clone https://libvirt.org/git/libvirt-php.git
-</pre>
-<p>
-It can also be browsed at
-</p>
-<pre>
-<a href="https://libvirt.org/git/?p=libvirt-php.git;a=summary">https://libvirt.org/git/?p=libvirt-php.git;a=summary</a>
+git clone https://gitlab.com/libvirt/libvirt-php.git
 </pre>
 
 <p></p>

docs/securityprocess.html.in

@@ -42,7 +42,7 @@
     <p>
       Information for all historical security issues is maintained in
       machine parsable format in the
-      <a href="https://libvirt.org/git/?p=libvirt-security-notice.git;a=log">libvirt-security-notice GIT repository</a> and
+      <a href="https://gitlab.com/libvirt/libvirt-security-notice">libvirt-security-notice GIT repository</a> and
       <a href="https://security.libvirt.org">published online</a>
       in text, HTML and XML formats. Security notices are published
       on the <a href="https://libvirt.org/contact.html#email">libvirt-announce mailing list</a>

docs/testapi.html.in

@@ -28,7 +28,7 @@
            and test scenarios.</li>
     </ul>
     <p> Libvirt-test-API is maintained using
-        <a href="https://libvirt.org/git/?p=libvirt-test-API.git">a GIT
+        <a href="https://gitlab.com/libvirt/libvirt-test-API">a GIT
         repository</a>, and comment, patches and reviews are carried
         on the <a href="contact.html">libvir-list</a> development list.</p>
   </body>

docs/testsuites.html.in

@@ -23,7 +23,7 @@
           <a href="ftp://libvirt.org/libvirt/tck/">download</a>, as a
           <a href="http://rpmfind.net/linux/rpm2html/search.php?query=libvirt-tck">package</a>
           in Fedora distributions, but best is probably to get
-          the <a href="https://libvirt.org/git/?p=libvirt-tck.git">version
+          the <a href="https://gitlab.com/libvirt/libvirt-tck">version
           from GIT</a>.
       </li>
       <li>the <a href="testapi.html">libvirt-test-API</a> is also a functional
@@ -32,7 +32,7 @@
           of libvirt. It is available separately as a
           <a href="ftp://libvirt.org/libvirt/libvirt-test-API/">download</a>,
           or directly get
-          the <a href="https://libvirt.org/git/?p=libvirt-test-API.git">version
+          the <a href="https://gitlab.com/libvirt/libvirt-test-API/">version
           from GIT</a>.
       </li>
     </ul>

docs/testtck.html.in

@@ -33,7 +33,7 @@
            Fedora Feature.</li>
     </ul>
     <p> Libvirt-TCK is maintained using
-        <a href="https://libvirt.org/git/?p=libvirt-tck.git">a GIT
+        <a href="https://gitlab.com/libvirt/libvirt-tck">a GIT
         repository</a>, and comment, patches and reviews are carried
         on the <a href="contact.html">libvir-list</a> development list.</p>
   </body>