From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Google Summer of Code 2013
Date: Tue, 5 Mar 2013 19:32:02 +0100 [thread overview]
Message-ID: <20130305193202.083a7562@skate> (raw)
In-Reply-To: <51358FD5.5040908@mind.be>
Dear Arnout Vandecappelle,
On Tue, 05 Mar 2013 07:25:25 +0100, Arnout Vandecappelle wrote:
> > Another solution is to get a little bit of sponsoring: getting one
> > BeagleBone and one i.MX6 based board sponsored shouldn't be too hard.
>
> Don't quote me on this, but I might be able to get my hands on a
> Gumstix Overo, with display and everything. Second-hand, of course.
Ok. Then I'll try to work on the administrative details to submit this
proposal. I think it's safe to say that participant to the GSoC this
year with only one proposal of topic is more reasonable. Having to
support multiple students could be difficult.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-03-05 18:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 23:42 [Buildroot] Report from the Buildroot Developers Meeting Thomas Petazzoni
2013-02-12 10:30 ` Stephan Hoffmann
2013-02-12 10:36 ` Thomas Petazzoni
2013-02-12 11:49 ` Stephan Hoffmann
2013-02-12 11:53 ` Thomas Petazzoni
2013-02-12 11:55 ` Stefan Fröberg
2013-02-12 14:14 ` Daniel Nyström
2013-02-12 14:18 ` Thomas Petazzoni
2013-02-12 15:57 ` Daniel Nyström
2013-02-13 18:55 ` Yann E. MORIN
2013-02-13 19:54 ` Thomas Petazzoni
2013-02-14 14:25 ` [Buildroot] Google Summer of Code 2013 Thomas Petazzoni
2013-03-03 13:43 ` Thomas Petazzoni
2013-03-03 17:29 ` Thomas De Schampheleire
2013-03-03 17:51 ` Stephan Hoffmann
2013-03-03 18:26 ` Thomas Petazzoni
2013-03-05 6:25 ` Arnout Vandecappelle
2013-03-05 18:32 ` Thomas Petazzoni [this message]
2013-03-06 8:57 ` Jérôme Pouiller
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=20130305193202.083a7562@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 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.