From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH 5/6] website/lts: add pre-filled content to mailto
Date: Thu, 19 Mar 2026 16:02:45 +0100 [thread overview]
Message-ID: <20260319150246.10937-5-thomas.perale@mind.be> (raw)
In-Reply-To: <20260319150246.10937-1-thomas.perale@mind.be>
Clicking on the mailto tag will prefill the email with the following
content:
> Thanks for showing interest in the Buildroot LTS Sponsorship. We would
> appreciate if you could introduce yourself and your company by
> answering the following questions: in which products do you use
> Buildroot ? How are you using Buildroot ? How many different
> configurations do you have ? How long do you support your products ?
Signed-off-by: Thomas Perale <thomas.perale@mind.be>
---
docs/website/lts.html | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/website/lts.html b/docs/website/lts.html
index 988415482c..fd684ab3a9 100644
--- a/docs/website/lts.html
+++ b/docs/website/lts.html
@@ -338,14 +338,14 @@
</div>
</div>
- <div id="sponsor" class="br-lts-section-header">
+ <a href="mailto:buildroot-lts@buildroot.org?subject=[buildroot-lts] Sponsorship information&body=Thanks for showing interest in the Buildroot LTS Sponsorship. We would appreciate if you could introduce yourself and your company by answering the following questions: in which products do you use Buildroot ? How are you using Buildroot ? How many different configurations do you have ? How long do you support your products ?" id="sponsor" class="br-lts-section-header">
<div class="br-lts-bg-grid"></div>
<div class="br-lts-title-box">Sponsor now !</div>
<div class="br-lts-decoration-dot"></div>
- </div>
+ </a>
<p>
Interested ? Contact us at
- <a href="mailto:buildroot-lts@buildroot.org">buildroot-lts@buildroot.org</a>
+ <a href="mailto:buildroot-lts@buildroot.org?subject=[buildroot-lts] Sponsorship information&body=Thanks for showing interest in the Buildroot LTS Sponsorship. We would appreciate if you could introduce yourself and your company by answering the following questions: in which products do you use Buildroot ? How are you using Buildroot ? How many different configurations do you have ? How long do you support your products ?">buildroot-lts@buildroot.org</a>
to learn more about the different sponsorship tiers and get all the
details about the sponsorship.
</p>
--
2.53.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-03-19 15:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 15:02 [Buildroot] [PATCH 1/6] website/sponsors.html: remove sense Thomas Perale via buildroot
2026-03-19 15:02 ` [Buildroot] [PATCH 2/6] website/sponsors.html: add IPComm as a silver sponsor Thomas Perale via buildroot
2026-03-19 15:02 ` [Buildroot] [PATCH 3/6] website/lts: remove the href on section Thomas Perale via buildroot
2026-03-19 15:02 ` [Buildroot] [PATCH 4/6] website/lts: fix section on small screens Thomas Perale via buildroot
2026-03-19 15:02 ` Thomas Perale via buildroot [this message]
2026-03-19 15:02 ` [Buildroot] [PATCH 6/6] website/lts: fix typos Thomas Perale via buildroot
2026-03-24 21:27 ` [Buildroot] [PATCH 1/6] website/sponsors.html: remove sense Julien Olivain via buildroot
2026-03-25 10:19 ` Thomas Perale 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=20260319150246.10937-5-thomas.perale@mind.be \
--to=buildroot@buildroot.org \
--cc=thomas.perale@mind.be \
/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