All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Developer Day at FOSDEM, 3-4 Feb 2014
Date: Wed, 13 Nov 2013 21:07:36 +0100	[thread overview]
Message-ID: <87d2m412wn.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20131113184420.GC24238@free.fr> (Yann E. MORIN's message of "Wed, 13 Nov 2013 19:44:20 +0100")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

Hi,

>> This meeting is open to Buildroot contributors and developers. With 70
>> different contributors to the 2013.11-rc release, I'd really like to
>> see this meeting having more participants than the usual core
>> members. So if you're contributing or using Buildroot, do not hesitate
>> to contact me to participate.

> Yes, it would be nice if users could make it, at least for the first day
> on Monday, so we can exchange experience and expectations, and have a
> good time together!

Exactly!

> Thank you Thomas for perfectly handling this DevDay, as usual! :-)

Couldn't agree more, thanks!

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2013-11-13 20:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13 18:12 [Buildroot] Buildroot Developer Day at FOSDEM, 3-4 Feb 2014 Thomas Petazzoni
2013-11-13 18:12 ` [Buildroot] [PATCH 1/2] docs: announce the upcoming Buildroot Developer Day Thomas Petazzoni
2013-11-13 18:40   ` Yann E. MORIN
2013-11-13 20:05   ` Peter Korsgaard
2013-11-13 20:31     ` Thomas Petazzoni
2013-11-13 18:12 ` [Buildroot] [PATCH 2/2] docs: add a page to thank our sponsors Thomas Petazzoni
2013-11-13 18:39   ` Yann E. MORIN
2013-11-13 20:06   ` Peter Korsgaard
2013-11-13 18:44 ` [Buildroot] Buildroot Developer Day at FOSDEM, 3-4 Feb 2014 Yann E. MORIN
2013-11-13 20:07   ` Peter Korsgaard [this message]
2013-11-13 19:09 ` 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=87d2m412wn.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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.