From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Survey for the next Buildroot Developer Day(s)
Date: Thu, 5 Jul 2012 18:00:10 +0200 [thread overview]
Message-ID: <20120705180010.2823fa87@skate> (raw)
In-Reply-To: <20120629103156.28bdd18b@skate>
Le Fri, 29 Jun 2012 10:31:56 +0200,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> a ?crit :
> In order to decide whether this Buildroot Developer Day should take
> place before or after ELCE and whether it should be one day or two
> days, we would like to invite interested parties to put their choices
> at
>
> http://www.doodle.com/fng2c8gw6r77xfbc
>
> Valid choices are:
>
> * Sunday
> * Saturday/Sunday
> * Thursday
> * Thursday/Friday
So far, four people have replied, and it seems that the majority was in
favor of the Saturday/Sunday solution. I know my colleague Maxime
can in fact come on Saturday/Sunday, it's just a little bit less
convenient, and Peter can't attend on Thursday/Friday due to the
KVM/oVirt conference.
So, let's settle on Saturday/Sunday, and make the announcement official:
The next Buildroot Developers Days will take place on Saturday 3rd
and Sunday 4th November in Barcelona, Spain, prior to the Embedded
Linux Conference Europe.
Other people interested in coming, please register to the Doodle
survey. Knowing the number of people, we will organize the necessary
logistics (i.e for just 4-5 people, we can just organize the meeting in
an hotel room, if we happen to be 7-8 people, then we'll have to find
some larger place).
Thanks for your participation,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-07-05 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 8:31 [Buildroot] Survey for the next Buildroot Developer Day(s) Thomas Petazzoni
2012-07-05 16:00 ` Thomas Petazzoni [this message]
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=20120705180010.2823fa87@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