From: Gerwin van der Kruis <gerwin@vanderkruis.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Who is going to speak at t-dose
Date: Sat, 29 Sep 2007 22:15:20 +0200 [thread overview]
Message-ID: <200709292215.20776.gerwin@vanderkruis.net> (raw)
In-Reply-To: <F08B4B67-A940-4674-ACB7-CFE77A28F44C@selfish.org>
On Saturday 29 September 2007 15:42, Holger Freyther wrote:
> Am 28.09.2007 um 17:25 schrieb Gerwin van der Kruis:
> > Hey All,
> >
> > We will be having a booth and a slot to speak at t-dose Netherlands.
> >
> > Are there people who are interested to speak there (Koen,MickeyL,
> > Likewise ??)
> >
> > Are there also people who interested in manning the booth ?
>
> Hi Gerwin,
>
> I will attend t-dose and could deliver a variation of koen's last ELC
> presentation.
>
Thanks so much I will tell jean-paul that you will give the presentation
Regards,
Gerwin
prev parent reply other threads:[~2007-09-29 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 15:25 Who is going to speak at t-dose Gerwin van der Kruis
2007-09-29 13:42 ` Holger Freyther
2007-09-29 20:15 ` Gerwin van der Kruis [this message]
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=200709292215.20776.gerwin@vanderkruis.net \
--to=gerwin@vanderkruis.net \
--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