[web] pages: convert http to https links

LEDE Commits lede-commits at lists.infradead.org
Fri Jul 1 22:21:43 PDT 2016

blogic pushed a commit to web.git, branch master:

commit b9fc0cd1583a97eb2f2256c1226640fd66edc95d
Author: Hauke Mehrtens <hauke at hauke-m.de>
AuthorDate: Thu May 5 15:59:57 2016 +0200

    pages: convert http to https links
    Use https for all internal and external links when possible.
    For security reasons we should prefer https over unencrypted http.
    Signed-off-by: Hauke Mehrtens <hauke at hauke-m.de>
 communication.txt |  4 ++--
 development.txt   | 20 ++++++++++----------
 index.txt         |  2 +-
 signing.txt       |  2 +-
 4 files changed, 14 insertions(+), 14 deletions(-)

diff --git a/communication.txt b/communication.txt
index 6e44adc..da6caae 100644
--- a/communication.txt
+++ b/communication.txt
@@ -15,9 +15,9 @@ using direct means of communication.
 The project offers the following mailing lists
-. http://lists.infradead.org/mailman/listinfo/lede-dev[lede-dev@lists.infradead.org] -
+. https://lists.infradead.org/mailman/listinfo/lede-dev[lede-dev@lists.infradead.org] -
   This list is used for submitting patches and general development related work
-. http://lists.infradead.org/mailman/listinfo/lede-adm[lede-adm@lists.infradead.org] - 
+. https://lists.infradead.org/mailman/listinfo/lede-adm[lede-adm@lists.infradead.org] - 
   This list is used for project organisational purposes. Anyone can
   subscribe and read this list, only committers may write to this list.
diff --git a/development.txt b/development.txt
index a13cac7..3a60000 100644
--- a/development.txt
+++ b/development.txt
@@ -11,7 +11,7 @@ by OpenWrt. While importing the sources the tree was normalised and some
 minor tweaks were made to committer names and mail addresses.
 All repositories can be browsed online through
-http://git.lede-project.org/[Gitweb] as well.
+https://git.lede-project.org/[Gitweb] as well.
 === Getting The _LEDE_ Code
@@ -19,7 +19,7 @@ Any _LEDE_ development happens in the main +source.git+ repository which is
 accessible via both HTTP and HTTPS:
-git clone http://git.lede-project.org/source.git
+git clone https://git.lede-project.org/source.git
 You can find a mirror of the repository on Github:
@@ -39,10 +39,10 @@ repositories mapping the various SVN directories and tags to proper Git
-git clone http://git.lede-project.org/openwrt/source.git
-git clone http://git.lede-project.org/openwrt/packages.git
-git clone http://git.lede-project.org/openwrt/feeds.git
-git clone http://git.lede-project.org/openwrt/docs.git
+git clone https://git.lede-project.org/openwrt/source.git
+git clone https://git.lede-project.org/openwrt/packages.git
+git clone https://git.lede-project.org/openwrt/feeds.git
+git clone https://git.lede-project.org/openwrt/docs.git
 === The Web Presence
@@ -52,7 +52,7 @@ http://www.methods.co.nz/asciidoc/[AsciiDoc] suite. Any changes made to the
 projects web site will be reflected in our +web.git+ repository:
-git clone http://git.lede-project.org/web.git
+git clone https://git.lede-project.org/web.git
 === Submitting Patches
@@ -60,18 +60,18 @@ git clone http://git.lede-project.org/web.git
 The biggest difference is that we now accept pull requests. The tree that shall
 be pulled from needs to be hosted publicly. Small fixes and minor patches can
 also be submitted via the
-http://lists.infradead.org/mailman/listinfo/lede-dev[development mailing list].
+https://lists.infradead.org/mailman/listinfo/lede-dev[development mailing list].
 Submissions should follow these rules
 . TBD
-All patches need to be sent in a format that they are listed in http://patchwork.ozlabs.org/project/lede/list/[patchwork].
+All patches need to be sent in a format that they are listed in https://patchwork.ozlabs.org/project/lede/list/[patchwork].
 If the patch does not get listed in patchwork then it won't get processed.
 === Reporting Bugs
-. Please report your bugs using our http://bugs.lede-project.org/[issue tracker]
+. Please report your bugs using our https://bugs.lede-project.org/[issue tracker]
 . When reporting bugs please make sure to
   .. Name the tree/revision
   .. Name the affected device
diff --git a/index.txt b/index.txt
index aeab673..55cf0d0 100644
--- a/index.txt
+++ b/index.txt
@@ -43,7 +43,7 @@ source code access and building instructions.
 If you do not consider yourself a developer but want to participate in
 maintaining documentation or in helping community members then don't hesitate
-to join our http://lists.infradead.org/mailman/listinfo/lede-dev[mailing list]
+to join our https://lists.infradead.org/mailman/listinfo/lede-dev[mailing list]
 or IRC channels to get in touch.
 === Endorsement
diff --git a/signing.txt b/signing.txt
index 8d8d8b2..4db2075 100644
--- a/signing.txt
+++ b/signing.txt
@@ -6,7 +6,7 @@ Release Signing
 == Signing Approach
 LEDE uses both https://www.gnupg.org/[GnuPG] and _usign_, a derivate of the
-OpenBSD http://www.openbsd.org/papers/bsdcan-signify.html[_signify_] utilitiy.
+OpenBSD https://www.openbsd.org/papers/bsdcan-signify.html[_signify_] utilitiy.
 The _OPKG_ package manager uses _usign_ Ed25519 signatures to verify repository
 metadata when installing packages while release image files are usually signed

More information about the lede-commits mailing list