From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Preyas via buildroot <buildroot@buildroot.org>
Cc: Preyas <preyas17@zohomail.in>
Subject: Re: [Buildroot] [PATCH] docs/website: switch HTTP links to HTTPS Update outdated insecure http links to https for buildroot.org, eLinux wiki, autobuild, and git-scm. Also fix downloads host from buildroot.net to buildroot.org.This reduces mixed-content issues and keeps references current.
Date: Sun, 4 Jan 2026 11:52:51 +0100 [thread overview]
Message-ID: <20260104115251.61b20331@windsurf> (raw)
In-Reply-To: <20251220111707.59273-1-preyas17@zohomail.in>
Hello Preyas,
On Sat, 20 Dec 2025 11:17:07 +0000
Preyas via buildroot <buildroot@buildroot.org> wrote:
> From: Preyas Sharma <preyas17@zohomail.in>
Thanks for your patch. However, the commit title is a bit messed up as
it is way too long. You might want to learn about the difference
between the commit "title" and the commit "body". Check for example
https://www.conventionalcommits.org/en/v1.0.0/.
Also, we cannot apply your patch as it is missing your Signed-off-by
line.
> <p>If you are not already familiar with using Git, we recommend
> - you visit <a href="http://git-scm.org">the Git
> + you visit <a href="https://git-scm.org">the Git
There is some spurious/unrelated indentation change here.
Could you rework your patch and send a new iteration?
Thanks a lot!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-01-04 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-20 11:17 [Buildroot] [PATCH] docs/website: switch HTTP links to HTTPS Update outdated insecure http links to https for buildroot.org, eLinux wiki, autobuild, and git-scm. Also fix downloads host from buildroot.net to buildroot.org.This reduces mixed-content issues and keeps references current Preyas via buildroot
2026-01-04 10:52 ` Thomas Petazzoni via buildroot [this message]
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=20260104115251.61b20331@windsurf \
--to=buildroot@buildroot.org \
--cc=preyas17@zohomail.in \
--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