From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org, buildroot-lts-sponsors@buildroot.org,
buildroot-users@buildroot.org
Subject: [Buildroot] Request for testimonals from users for Buildroot 25y talk
Date: Sun, 13 Sep 2026 22:40:40 +0200 [thread overview]
Message-ID: <87a4pkx4tz.fsf@dell.be.48ers.dk> (raw)
Hi,
Buildroot turns 25! And to celebrate, we are doing a talk about the
history at the Embedded Linux Conference in Prague, October 9th:
https://osselceu2026.sched.com/event/2Ragq/buildroot-at-25-a-quarter-century-of-making-embedded-linux-easy-peter-korsgaard-barco?
For this talk it would be interesting to give some examples and
testimonals from companies or projects using Buildroot, E.G.:
- Name of company / project
- What product(s), ideally with a picture
- How long have you used Buildroot for this?
- Any additional notes or testimonals, why Buildroot?
Please reply to the list (or me directly if you prefer), then I will
collect the responses together and pick a selection for the talk.
Thanks in advance!
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
reply other threads:[~2026-09-13 20:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87a4pkx4tz.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot-lts-sponsors@buildroot.org \
--cc=buildroot-users@buildroot.org \
--cc=buildroot@buildroot.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.