Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Subject: [Buildroot] Buildroot at FOSDEM 2025 !
Date: Tue, 21 Jan 2025 11:22:51 +0100	[thread overview]
Message-ID: <20250121112251.10530b87@windsurf> (raw)

Hello,

If there are Buildroot enthusiasts at FOSDEM 2025:

- We have a tradition of having a dinner of the broader Buildroot
  community on Saturday night, in Brussels city center. Many of the
  maintainers will be there, as well as several contributors.

  If you're interested in joining, let me know and I'll add you to the
  list.

- We also have the Buildroot Developers Days right after FOSDEM, on
  Monday/Tuesday/Wednesday. We already have 10 people planning to
  attend.

  If you're interested, have a look
  at https://elinux.org/Buildroot:DeveloperDaysFOSDEM2025

See you at FOSDEM!

Best regards,

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

                 reply	other threads:[~2025-01-21 10:22 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=20250121112251.10530b87@windsurf \
    --to=buildroot@buildroot.org \
    --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