From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: [Buildroot] Next Buildroot Developers meeting: Sep 14-15 in Vienna
Date: Thu, 13 Jun 2024 23:29:39 +0200 [thread overview]
Message-ID: <20240613232939.11bd0f54@windsurf> (raw)
Hello,
I'm happy to announce that the next Buildroot Developers Meeting will
take place on September 14/15 in Vienna, right before the Open Source
Summit Europe 2024.
Please see:
https://elinux.org/Buildroot:DeveloperDaysELCE2024
for some details regarding this hackathon, as well for registration.
We encourage Buildroot contributors to consider attending this
hackathon. It's a super nice way of making progress on Buildroot
development, reducing the backlog of patches, fixing issues, and simply
meeting each other in person.
Three of the maintainers have confirmed their presence to this
hackathon.
The event is free, after registration.
Do not hesitate to contact me if you have any question. We hope to see
several contributors participate to this event!
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:[~2024-06-13 21:29 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=20240613232939.11bd0f54@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 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.