diff mbox series

[pacman-dev,v2,1/2] Update broken links pointing to git.archlinux.org

Message ID 20210814101329.492010-2-hugo@barrera.io
State Superseded, archived
Headers show
Series [pacman-dev,v2,1/2] Update broken links pointing to git.archlinux.org | expand

Commit Message

Hugo Osvaldo Barrera Aug. 14, 2021, 10:13 a.m. UTC 
All of these links are broken since the recent move to
gitlab.archlinux.org.

A few projects are, apparently, only available on GitHub, so I've linked
to that source (hopefully that's only temporary).

For git-clone URLs, I've opted for the https URLs since those can be
used by anyone -- whereas the ssh URLs require the user to be registered
on the gitlab instance which is not open to the public yet.

Signed-off-by: Hugo Osvaldo Barrera <hugo@barrera.io>
---
 doc/index.asciidoc              | 11 +++++------
 doc/submitting-patches.asciidoc |  2 +-
 doc/translation-help.asciidoc   |  2 +-
 3 files changed, 7 insertions(+), 8 deletions(-)

Comments

Allan McRae Sept. 3, 2021, 12:53 p.m. UTC | #1 
On 14/8/21 8:13 pm, Hugo Osvaldo Barrera wrote:
> All of these links are broken since the recent move to
> gitlab.archlinux.org.
> 
> A few projects are, apparently, only available on GitHub, so I've linked
> to that source (hopefully that's only temporary).
> 
> For git-clone URLs, I've opted for the https URLs since those can be
> used by anyone -- whereas the ssh URLs require the user to be registered
> on the gitlab instance which is not open to the public yet.
> 
> Signed-off-by: Hugo Osvaldo Barrera <hugo@barrera.io>
> ---

Thanks - I have made one change

<snip>

>  which will fetch the full development history into a directory named pacman.
>  You can browse the source as well using
> -link:https://git.archlinux.org/pacman.git/[cgit]. HTTP/HTTPS URLs are also
> -available for cloning purposes; these URLs are listed at the above page.
> +link:https://gitlab.archlinux.org/pacman/pacman/-/tree/master[gitlab].
>  

link:https://gitlab.archlinux.org/pacman/pacman/


Allan
diff mbox series

Patch

diff --git a/doc/index.asciidoc b/doc/index.asciidoc
index 47295f9b..f8890961 100644
--- a/doc/index.asciidoc
+++ b/doc/index.asciidoc
@@ -59,11 +59,11 @@  configuration files dealing with pacman.
 Changelog
 ~~~~~~~~~
 For a good idea of what is going on in pacman development, take a look at the
-link:https://git.archlinux.org/pacman.git/[Git summary page] for the
+link:https://gitlab.archlinux.org/pacman/pacman[Git summary page] for the
 project.
 
 See the most recent
-link:https://git.archlinux.org/pacman.git/tree/NEWS[NEWS]
+link:https://gitlab.archlinux.org/pacman/pacman/-/blob/master/NEWS[NEWS]
 file for a not-as-frequently-updated list of changes. However, this should
 contain the biggest changes in a format more concise than the commit log.
 
@@ -220,12 +220,11 @@  these trees).
 
 The current development tree can be fetched with the following command:
 
-	git clone git://git.archlinux.org/pacman.git pacman
+	git clone https://gitlab.archlinux.org/pacman/pacman.git
 
 which will fetch the full development history into a directory named pacman.
 You can browse the source as well using
-link:https://git.archlinux.org/pacman.git/[cgit]. HTTP/HTTPS URLs are also
-available for cloning purposes; these URLs are listed at the above page.
+link:https://gitlab.archlinux.org/pacman/pacman/-/tree/master[gitlab].
 
 If you are interested in hacking on pacman, it is highly recommended you join
 the mailing list mentioned above, as well as take a quick glance at our
@@ -243,7 +242,7 @@  Although the package manager itself is quite simple, many scripts have been
 developed that help automate building and installing packages. These are used
 extensively in link:https://archlinux.org/[Arch Linux]. Most of these utilities
 are available in the Arch Linux projects
-link:https://git.archlinux.org/[code browser].
+link:https://gitlab.archlinux.org/archlinux[code browser].
 
 Utilities available:
 
diff --git a/doc/submitting-patches.asciidoc b/doc/submitting-patches.asciidoc
index 88b58ca5..14b80b61 100644
--- a/doc/submitting-patches.asciidoc
+++ b/doc/submitting-patches.asciidoc
@@ -20,7 +20,7 @@  started with GIT if you have not worked with it before.
 
 The pacman code can be fetched using the following command:
 
-	git clone git://git.archlinux.org/pacman.git
+	git clone https://gitlab.archlinux.org/pacman/pacman.git
 
 
 Creating your patch
diff --git a/doc/translation-help.asciidoc b/doc/translation-help.asciidoc
index 5a67a2d6..4301852d 100644
--- a/doc/translation-help.asciidoc
+++ b/doc/translation-help.asciidoc
@@ -78,7 +78,7 @@  Incremental Updates
 If you have more advanced needs you will have to get a copy of the pacman
 repository.
 
-	git clone git://git.archlinux.org/pacman.git pacman
+	git clone https://gitlab.archlinux.org/pacman/pacman.git
 
 Next, you will need to run `./autogen.sh` and `./configure` in the base
 directory to generate the correct Makefiles. At this point, all necessary