All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markos Chandras <markos.chandras@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Dates for the next Buildroot Developers Meeting
Date: Mon, 12 Aug 2013 09:17:45 +0100	[thread overview]
Message-ID: <CAG2jQ8im=rfRdMw+ypL4djNuCfyCnYX6eN4P73YDWYjDo7ERdw@mail.gmail.com> (raw)
In-Reply-To: <20130715212511.GB12096@free.fr>

On 15 July 2013 22:25, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> Thomas, Peter, All,
>
> On 2013-07-04 18:17 +0200, Yann E. MORIN spake thusly:
>> On 2013-07-04 10:48 +0200, Thomas Petazzoni spake thusly:
>> > On Thu, 04 Jul 2013 10:43:14 +0200, Peter Korsgaard wrote:
>> > >  Thomas> The next Embedded Linux Conference Europe will take place on
>> > >  Thomas> Thursday 24th and Friday 25th of October, in Edinburgh,
>> > >  Thomas> UK. Since LinuxCon Europe will take place at the beginning of
>> > >  Thomas> the week (from Monday to Wednesday), I believe the best date
>> > >  Thomas> for our meeting will be on Saturday 26th and Sunday 27th.
>> > >
>> > >  Peter> I'm planning on attending the gstreamer conference (22-23th), so the
>> > >  Peter> weekend after would also fit me best.
>> > >
>> > >  Peter> If anyone disagrees, please let us know because I would like to book
>> > >  Peter> flight/hotel soon.
>> > >
>> > > I've now booked conference/hotel/flights (21-27th). Anybody else?
>
> Ok, everything is under control!
>
> LCE: registered
> ELCE: registered
> Hotel: booked
> Flight: processing
>
> I'll be in Edimburgh starting the 20st late in the afternoon.
> I'll be leaving on the 28th in the morning.
>
> So, I'll be attending the DevDay Saturday & Sunday.
>
> /me is looking forward to being there! :-)
>
> Regards,
> Yann E. MORIN.
>
> --
> .-----------------.--------------------.------------------.--------------------.
> |  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
> | +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
> | +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
> | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
> '------------------------------^-------^------------------^--------------------'
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

I will also attend the Buildroot DevDays as well :)

-- 
Regards,
Markos Chandras

  reply	other threads:[~2013-08-12  8:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-25 20:23 [Buildroot] Dates for the next Buildroot Developers Meeting Thomas Petazzoni
2013-06-19  8:41 ` Peter Korsgaard
2013-07-04  8:43   ` Peter Korsgaard
2013-07-04  8:48     ` Thomas Petazzoni
2013-07-04 16:17       ` Yann E. MORIN
2013-07-15 21:25         ` Yann E. MORIN
2013-08-12  8:17           ` Markos Chandras [this message]
2013-09-23  7:41             ` Samuel Martin
2013-10-04  9:34 ` Alexander Lukichev
2013-10-04  9:43   ` [Buildroot] Date of the FOSDEM 2014 meeting? Thomas Petazzoni
2013-10-04 12:44     ` Peter Korsgaard
2013-10-04 16:39     ` Yann E. MORIN
2013-10-07  6:48     ` Arnout Vandecappelle
2013-10-08  9:41     ` Thomas De Schampheleire

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='CAG2jQ8im=rfRdMw+ypL4djNuCfyCnYX6eN4P73YDWYjDo7ERdw@mail.gmail.com' \
    --to=markos.chandras@gmail.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.