From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Patchwork session, March 8th
Date: Mon, 7 Mar 2016 21:19:14 +0100 [thread overview]
Message-ID: <20160307211914.3d33efe5@free-electrons.com> (raw)
Hello,
Our next patchwork session is scheduled tomorrow, on March 8th, see:
https://framadate.org/WEmxCql13oXFhbMs
For now just Yegor and me have confirmed their participation, Arnout
and Samuel said they might be appear.
Could other people join? Peter? Yann? Gustavo? Others?
I've started up a Wiki page at
http://elinux.org/Buildroot:PatchworkSessions to list ahead of times
the list of patches/topics we want to discuss/work on. On my side, I'll
fill it tomorrow with a list of patches I'm not sure what to do with
and therefore need to be discussed.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next reply other threads:[~2016-03-07 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 20:19 Thomas Petazzoni [this message]
2016-03-08 11:30 ` [Buildroot] Patchwork session, March 8th Peter Korsgaard
2016-03-08 11:35 ` Vicente Olivert Riera
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=20160307211914.3d33efe5@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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