From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Setting the dates of the next Buildroot Developers meeting
Date: Wed, 22 Oct 2014 14:21:49 +0200 [thread overview]
Message-ID: <20141022142149.7ec8eebf@free-electrons.com> (raw)
Hello all,
The last Buildroot Developers meeting has just finished last week, and
it's already time to think about the next one. It typically takes place
right after the FOSDEM conference in Brussels.
This year, the FOSDEM takes place on Saturday 31th January and Sunday
1st February. This would mean that the Buildroot Developers Meeting
should normally take place on Monday 2nd and Tuesday 3rd February.
Is this fine for everyone, or do we have reasons to have the meeting
*before* FOSDEM (Thursday 29th and Friday 30th January) instead ?
Let me know quickly what your preference is, so that I can arrange the
logistics.
See the event page I've started at:
http://elinux.org/Buildroot:DeveloperDaysFOSDEM2015
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
reply other threads:[~2014-10-22 12:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20141022142149.7ec8eebf@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