From: "Alexis Lothoré via buildroot" <buildroot@buildroot.org>
To: "Baruch Siach" <baruch@tkos.co.il>,
"Alexis Lothoré via buildroot" <buildroot@buildroot.org>
Cc: "Alexis Lothoré" <alexis.lothore@bootlin.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH] docs/manual/getting: fix dead link
Date: Mon, 22 Sep 2025 16:11:15 +0200 [thread overview]
Message-ID: <DCZE1NNPYVQP.VA152ACRNNYT@bootlin.com> (raw)
In-Reply-To: <87wm5sosjs.fsf@tarshish>
Hi Baruch,
On Sun Sep 21, 2025 at 3:15 PM CEST, Baruch Siach wrote:
> Hi Alexis,
>
> On Sun, Sep 21 2025, Alexis Lothoré via buildroot wrote:
[...]
>> If you want to follow development, you can use the daily snapshots or
>> make a clone of the Git repository. Refer to the
>> -http://buildroot.org/download[Download page] of the Buildroot website
>> +http://buildroot.org/download.html[Download page] of the Buildroot website
>
> Maybe switch to https while at it? This link redirects there anyway.
Sure. But in this case, I guess it does not make sense to do it only for
this link, and it should be done for any link pointing to buildroot.org:
$ grep -ri "http://.*buildroot.org" ~/src/buildroot/docs/manual
/home/alexis/src/buildroot/docs/manual/contribute.adoc:All build results are available at http://autobuild.buildroot.org[],
/home/alexis/src/buildroot/docs/manual/contribute.adoc:statistics are at http://autobuild.buildroot.org/stats.php[]. Every day,
/home/alexis/src/buildroot/docs/manual/contribute.adoc: http://git.buildroot.org/buildroot-test/tree/utils/br-reproduce-build[br-reproduce-build]
/home/alexis/src/buildroot/docs/manual/contribute.adoc:Fixes: http://autobuild.buildroot.org/results/51000a9d4656afe9e0ea6f07b9f8ed374c2e4069
/home/alexis/src/buildroot/docs/manual/resources.adoc:http://lists.buildroot.org/mailman/listinfo/buildroot[mailing list info
/home/alexis/src/buildroot/docs/manual/resources.adoc:http://lists.buildroot.org/pipermail/buildroot[Mailman] or at
/home/alexis/src/buildroot/docs/manual/getting.adoc:Release tarballs are available at http://buildroot.org/downloads/[].
/home/alexis/src/buildroot/docs/manual/getting.adoc:http://buildroot.org/download.html[Download page] of the Buildroot website
/home/alexis/src/buildroot/docs/manual/manual.adoc:http://git.buildroot.org/buildroot/tree/COPYING?id={sys:git rev-parse HEAD}[COPYING]
/home/alexis/src/buildroot/docs/manual/adding-packages-tips.adoc:Buildroot runs http://autobuild.buildroot.org/[autobuilders] which
If maintainers are fine with that, I can add a dedicated commit in a v2.
Thanks,
Alexis
--
Alexis Lothoré, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-09-22 14:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-21 12:39 [Buildroot] [PATCH] docs/manual/getting: fix dead link Alexis Lothoré via buildroot
2025-09-21 13:15 ` Baruch Siach via buildroot
2025-09-22 14:11 ` Alexis Lothoré via buildroot [this message]
2025-09-22 20:06 ` Julien Olivain via buildroot
2025-09-22 20:33 ` Alexis Lothoré via buildroot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DCZE1NNPYVQP.VA152ACRNNYT@bootlin.com \
--to=buildroot@buildroot.org \
--cc=alexis.lothore@bootlin.com \
--cc=baruch@tkos.co.il \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox