From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Online Buildroot Developers Meeting, November 2
Date: Mon, 2 Nov 2020 23:37:02 +0100 [thread overview]
Message-ID: <20201102233702.4774c08d@windsurf> (raw)
Hello,
Tomorrow November 2 is the first Tuesday of November. Not only this
means it's US Elections Day, but it also means that it's our
traditional online Buildroot Developers Meeting.
All of the four co-maintainers have confirmed their presence for the
meeting, but we of course would like many others to participate.
The principle is quite simple: we meet on IRC, define some patches to
look at, distribute who is going to look at what, we try to make
progress on pending patch series. You can participate by
reviewing/testing pending series, by pointing us to patches you think
are ready to apply, or generally to hack on Buildroot.
Let's meet tomorrow at 9 PM CET on #buildroot @ Freenode !
More details:
https://elinux.org/Buildroot:RegularVirtualMeeting
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next reply other threads:[~2020-11-02 22:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 22:37 Thomas Petazzoni [this message]
2020-11-03 9:30 ` [Buildroot] Online Buildroot Developers Meeting, November 2 Peter Korsgaard
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=20201102233702.4774c08d@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