From: Philippe De Swert <philippedeswert@scarlet.be>
To: openembedded-devel@openembedded.org
Subject: Re: OpenEmbedded @ FOSDEM - CfP - deadline: 2008-12-20
Date: Thu, 15 Jan 2009 09:39:08 +0200 [thread overview]
Message-ID: <1232005148.2941.3.camel@localhost.localdomain> (raw)
In-Reply-To: <494205F8.2040400@gmx.net>
Hi all,
On Fri, 2008-12-12 at 07:34 +0100, Robert Schuster wrote:
> Hi,
> as you read in the last mail OpenEmbedded will not get it own room at
> the upcomming FOSDEM. Nevertheless you will have the chance of
> presenting your OE-related talk as part of the 'Embedded devroom'.
>
> The Embedded devroom is organized by Philippe de Swert. So eventually
> all organisation stuff concerning the room and your talk has to be done
> with him.
Anybody having submitted anything as I have not recieved anything yet
and really need to make the program...
Please send stuff to me directly to be sure I got it.
Thank you,
Philippe
next prev parent reply other threads:[~2009-01-15 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 6:34 OpenEmbedded @ FOSDEM - CfP - deadline: 2008-12-20 Robert Schuster
2009-01-15 7:39 ` Philippe De Swert [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-12 14:13 Philippe De Swert
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=1232005148.2941.3.camel@localhost.localdomain \
--to=philippedeswert@scarlet.be \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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 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.