From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Report of the Buildroot Developers meeting @ ELCE 2018
Date: Wed, 31 Oct 2018 11:43:48 +0100 [thread overview]
Message-ID: <20181031114348.5a95ce59@windsurf> (raw)
Hello,
On October 20-21, a number of Buildroot developers gathered in
Edinburgh (UK) for a 2-day Developers meeting. A short report for this
meeting is now available at (thanks Arnout):
https://elinux.org/Buildroot:DeveloperDaysELCE2018#Meeting_report
We discussed:
- top level parallel build
- reproducible builds
- doing more testing
- hardening support in the toolchain wrapper
- LTO support
- S01logging updates
- Download of extra downloads with identical file names
Also, we had a general assembly of the Buildroot Association. And
finally, most of the time was dedicated to actual hacking on Buildroot,
with a strong focus on going through the patchwork backlog, and
reviewing, replying and merging as many patches as possible. By the end
of ELCE, the backlog of patches was down to ~200 patches.
Once again, I would like to thank our sponsors for this event:
- Mind, https://www.mind.be/
- Amarula Solutions, https://www.amarulasolutions.com/
- TK Open Systems, http://tkos.co.il/
- Bootlin, https://www.bootlin.com
- Logilin, https://www.logilin.fr/
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next reply other threads:[~2018-10-31 10:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 10:43 Thomas Petazzoni [this message]
2018-10-31 10:53 ` [Buildroot] Report of the Buildroot Developers meeting @ ELCE 2018 Thomas Petazzoni
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=20181031114348.5a95ce59@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 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.