From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Patchwork day March 2013
Date: Mon, 4 Mar 2013 11:05:41 +0100 [thread overview]
Message-ID: <20130304110541.4ae1a82e@skate> (raw)
Hello,
At the end of the last Buildroot Developers Day, Arnout and I have been
discussing the idea of organizing more regular meetings, that would be
held virtually on IRC. The goal of those meetings would be to go
through the list of pending patches
(http://patchwork.ozlabs.org/project/buildroot/list/) and do some
review/testing on them in order to help get them applied. Doing that
together on the same day:
* Allows to synchronize quickly through IRC who is working on which
patches.
* Hopefully get some patches applied quickly, either if Peter
participates, or if he doesn't, someone else accumulate the patches
that the other people agree with, and sends a big pull request to
Peter at the end of the day.
* Make fun things :)
In order to get things started, I'm proposing a quick poll to decide on
a first day for the month of March:
http://www.doodle.com/up4fzf7qa8bm9bqp
If you're interested, please put our available dates in the poll, and
I'll send in a few days a mail with the selected date.
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next reply other threads:[~2013-03-04 10:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 10:05 Thomas Petazzoni [this message]
2013-03-17 15:14 ` [Buildroot] Buildroot Patchwork day March 2013 Yann E. MORIN
2013-03-18 22:22 ` 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=20130304110541.4ae1a82e@skate \
--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