From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Travel sponsorship for the Buildroot Developers Meeting
Date: Sun, 12 Jan 2020 22:05:11 +0100 [thread overview]
Message-ID: <20200112220511.291b6fef@windsurf> (raw)
Hello,
We are happy to announce that the Buildroot Association has granted
travel sponsorship to Adam Duskett, so that he can travel from the US
to Brussels for the next Buildroot Developers Meeting.
We would like to thank all the companies and individuals who donated to
the Buildroot Association, their donation make this kind of travel
sponsorship possible. If you are interested in donating or being a
member of the Buildroot Association, see
https://buildroot.org/association.html for more details.
Also, if you are a Buildroot contributor, interested in participating
to the Buildroot Meeting, but cannot attend due to the cost of travel,
do not hesitate to contact us. We believe it is very useful for
Buildroot contributors to meet each other, and we are therefore willing
to spend some of the Buildroot Association budget on travel sponsorship.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
reply other threads:[~2020-01-12 21:05 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=20200112220511.291b6fef@windsurf \
--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