From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ELCE] Nov. 5.-7. meeting
Date: Mon, 24 Sep 2012 17:05:30 +0200 [thread overview]
Message-ID: <201209241705.30659.marex@denx.de> (raw)
In-Reply-To: <50606484.4090903@denx.de>
Dear Stefan Roese,
> Hi Wolfgang,
>
> On 09/24/2012 03:39 PM, Wolfgang Denk wrote:
> >>> I won't make it, sorry. Best would be to schedule such an event with a
> >>> bit more time to prepare. Isn't there a suitable Linux/FOSS meeting in
> >>> Spring 2013 in Europe?
> >>
> >> FOSDEM maybe?
> >
> > FOSDEM traditionally collides with the Embedded World trade show.
>
> Not this time:
>
> FOSDEM: 2. - 3. February
> EM 2013: 26. - 28. February
And not the last time ;-)
[...]
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-09-24 15:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 23:21 [U-Boot] [ELCE] Nov. 5.-7. meeting Marek Vasut
2012-09-22 13:43 ` Otavio Salvador
2012-09-24 9:41 ` Wolfgang Denk
2012-09-24 9:52 ` Stefan Roese
2012-09-24 13:34 ` Marek Vasut
2012-09-24 13:39 ` Wolfgang Denk
2012-09-24 13:47 ` Stefan Roese
2012-09-24 15:05 ` Marek Vasut [this message]
2012-09-24 12:27 ` Roberto Nibali
2012-09-24 16:17 ` Tom Rini
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=201209241705.30659.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/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