From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Patchwork Day May 2013
Date: Tue, 7 May 2013 16:18:35 +0200 [thread overview]
Message-ID: <20130507161835.1a16b5af@skate> (raw)
Hello,
Since the first Patchwork Day was useful, let's try to set up a second
one. I've created a Doodle poll to find a date that would work for
several developers: http://www.doodle.com/nrdyzesxknv8gavx.
For those who don't know, the goal of a Patchwork Day is to go through
patches sitting in Patchwork, or bugs waiting in the Bugzilla, a find
a solution for those. Either rework the patch and submit an updated
version, or do some review to encourage the submitter to send a new
version, or discuss is the patch should be rejected or not, etc.
Contributors welcome.
Best regards,
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-05-07 14:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 14:18 Thomas Petazzoni [this message]
2013-05-13 20:40 ` [Buildroot] Buildroot Patchwork Day May 2013 Yann E. MORIN
2013-05-13 21:05 ` 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=20130507161835.1a16b5af@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