From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OEDEM: info
Date: Thu, 14 Oct 2010 09:26:54 +0200 [thread overview]
Message-ID: <4CB6B0BE.70108@atmel.com> (raw)
In-Reply-To: <20101013175113.GF11514@denix.org>
Le 13/10/2010 19:51, Denys Dmytriyenko :
> On Tue, Oct 12, 2010 at 10:53:14PM +0200, Frans Meulenbroeks wrote:
>> 2010/10/12 Raffaele Recalcati <lamiaposta71@gmail.com>:
>>> I'm interested in attending to OEDEM for friday morning.
>>> I have added myself to the list "Attending for sure", even if I'm not
>>> a skilled OE developer.
>>> I hope that I have done the right thing.
>>>
>>> See you in Cambridge,
>>> Recalcati
>>
>> Raffaele, glad to see you here.
>>
>> Technical question to the board:
>> I thought the eV meeting was planned for fri morning.
>> Is that open for non-members. Not that I have objections against it
>> being open, but better get this clear upfront.
>
> Since Raffaele and Fabio are only coming for Friday morning, should we try to
> discuss technical aspects first, and leave organizational ones (i.e. eV GA)
> for later?
I will also be in Cambridge and would like to meet you guys. I am not
sure to be able to attend to whole OEDEM but I would be happy to meet
you on Friday (morning).
So, if we can discuss technical aspects this particular day, It may be
easier for me to come.
Best regards,
--
Nicolas Ferre
next prev parent reply other threads:[~2010-10-14 7:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 15:36 OEDEM: info Raffaele Recalcati
2010-10-12 16:03 ` Stefan Schmidt
2010-10-12 20:53 ` Frans Meulenbroeks
2010-10-13 17:51 ` Denys Dmytriyenko
2010-10-13 18:00 ` Frans Meulenbroeks
2010-10-14 11:01 ` Graeme Gregory
2010-10-14 11:09 ` Frans Meulenbroeks
2010-10-14 7:26 ` Nicolas Ferre [this message]
2010-10-14 12:19 ` Philip Balister
2010-10-18 10:11 ` Richard Purdie
2010-10-18 10:24 ` Philip Balister
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=4CB6B0BE.70108@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=openembedded-devel@lists.openembedded.org \
/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