From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Developers Meeting: 4-6 February 2019, Brussels
Date: Mon, 3 Dec 2018 17:04:46 +0100 [thread overview]
Message-ID: <20181203170446.754ebcb3@windsurf.home> (raw)
Hello,
The next Buildroot Developers meeting will take place on February 4, 5
and 6 in Brussels, right after the FOSDEM conference.
You'll notice that we switched to a 3-day format instead of the usual
2-day format. Attending the full event is not mandatory: if you can
only join for 1 day or 2 days, you are also welcome.
As usual, we will be hosted by Google, our sponsor for many years,
providing an excellent meeting room in the center of Brussels.
Registration is free, just write your name on the Wiki page:
https://elinux.org/Buildroot:DeveloperDaysFOSDEM2019
If you are interested in participating and are a regular Buildroot
contributor but have issues with the travel costs, please contact me
privately. We do have some (limited) budget for travel expenses if that
allows regular contributors to participate to the meeting.
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
reply other threads:[~2018-12-03 16:04 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=20181203170446.754ebcb3@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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