docs/manual: update links to buildroot.org from http to https

Many links pointing to buildroot.org are still prefixed with HTTP.
Update those to HTTPS.

Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com>
Signed-off-by: Julien Olivain <ju.o@free.fr>
This commit is contained in:
Alexis Lothoré
2025-09-23 09:10:15 +02:00
committed by Julien Olivain
parent 7660818b4b
commit 6f29c81703
5 changed files with 10 additions and 10 deletions

View File

@@ -85,7 +85,7 @@ under various conditions: does it build for all architectures? Does it
build with the different C libraries? Does it need threads, NPTL? And build with the different C libraries? Does it need threads, NPTL? And
so on... so on...
Buildroot runs http://autobuild.buildroot.org/[autobuilders] which Buildroot runs https://autobuild.buildroot.org/[autobuilders] which
continuously test random configurations. However, these only build the continuously test random configurations. However, these only build the
`master` branch of the git tree, and your new fancy package is not yet `master` branch of the git tree, and your new fancy package is not yet
there. there.

View File

@@ -40,8 +40,8 @@ with a random selection of packages. With the large commit activity on
Buildroot, these autobuilders are a great help in detecting problems Buildroot, these autobuilders are a great help in detecting problems
very early after commit. very early after commit.
All build results are available at http://autobuild.buildroot.org[], All build results are available at https://autobuild.buildroot.org[],
statistics are at http://autobuild.buildroot.org/stats.php[]. Every day, statistics are at https://autobuild.buildroot.org/stats.php[]. Every day,
an overview of all failed packages is sent to the mailing list. an overview of all failed packages is sent to the mailing list.
Detecting problems is great, but obviously these problems have to be Detecting problems is great, but obviously these problems have to be
@@ -58,7 +58,7 @@ basically two things that can be done:
these steps: these steps:
. Check if you can reproduce the problem by building with the same . Check if you can reproduce the problem by building with the same
configuration. You can do this manually, or use the configuration. You can do this manually, or use the
http://git.buildroot.org/buildroot-test/tree/utils/br-reproduce-build[br-reproduce-build] https://git.buildroot.org/buildroot-test/tree/utils/br-reproduce-build[br-reproduce-build]
script that will automatically clone a Buildroot git repository, script that will automatically clone a Buildroot git repository,
checkout the correct revision, download and set the right checkout the correct revision, download and set the right
configuration, and start the build. configuration, and start the build.
@@ -73,7 +73,7 @@ basically two things that can be done:
In the commit message of a patch fixing an autobuild failure, add a In the commit message of a patch fixing an autobuild failure, add a
reference to the build result directory, as follows: reference to the build result directory, as follows:
---- ----
Fixes: http://autobuild.buildroot.org/results/51000a9d4656afe9e0ea6f07b9f8ed374c2e4069 Fixes: https://autobuild.buildroot.org/results/51000a9d4656afe9e0ea6f07b9f8ed374c2e4069
---- ----
=== Reviewing and testing patches === Reviewing and testing patches

View File

@@ -8,7 +8,7 @@ Buildroot releases are made every 3 months, in February, May, August and
November. Release numbers are in the format YYYY.MM, so for example November. Release numbers are in the format YYYY.MM, so for example
2013.02, 2014.08. 2013.02, 2014.08.
Release tarballs are available at http://buildroot.org/downloads/[]. Release tarballs are available at https://buildroot.org/downloads/[].
For your convenience, a https://www.vagrantup.com/[Vagrantfile] is For your convenience, a https://www.vagrantup.com/[Vagrantfile] is
available in `support/misc/Vagrantfile` in the Buildroot source tree available in `support/misc/Vagrantfile` in the Buildroot source tree
@@ -32,5 +32,5 @@ vagrant up
If you want to follow development, you can use the daily snapshots or If you want to follow development, you can use the daily snapshots or
make a clone of the Git repository. Refer to the make a clone of the Git repository. Refer to the
http://buildroot.org/download.html[Download page] of the Buildroot website https://buildroot.org/download.html[Download page] of the Buildroot website
for more details. for more details.

View File

@@ -9,7 +9,7 @@ Buildroot {sys:echo $BR2_VERSION} manual generated on {localdate}
The Buildroot manual is written by the Buildroot developers. The Buildroot manual is written by the Buildroot developers.
It is licensed under the GNU General Public License, version 2. Refer to the It is licensed under the GNU General Public License, version 2. Refer to the
http://git.buildroot.org/buildroot/tree/COPYING?id={sys:git rev-parse HEAD}[COPYING] https://git.buildroot.org/buildroot/tree/COPYING?id={sys:git rev-parse HEAD}[COPYING]
file in the Buildroot sources for the full text of this license. file in the Buildroot sources for the full text of this license.
Copyright (C) The Buildroot developers <buildroot@buildroot.org> Copyright (C) The Buildroot developers <buildroot@buildroot.org>

View File

@@ -17,12 +17,12 @@ main method of interaction for Buildroot users and developers.
+ +
Only subscribers to the Buildroot mailing list are allowed to post to Only subscribers to the Buildroot mailing list are allowed to post to
this list. You can subscribe via the this list. You can subscribe via the
http://lists.buildroot.org/mailman/listinfo/buildroot[mailing list info https://lists.buildroot.org/mailman/listinfo/buildroot[mailing list info
page]. page].
+ +
Mails that are sent to the mailing list are also available in the Mails that are sent to the mailing list are also available in the
mailing list archives, available through mailing list archives, available through
http://lists.buildroot.org/pipermail/buildroot[Mailman] or at https://lists.buildroot.org/pipermail/buildroot[Mailman] or at
https://lore.kernel.org/buildroot/[lore.kernel.org]. https://lore.kernel.org/buildroot/[lore.kernel.org].
IRC:: IRC::