From: Philip Balister <philip@balister.org>
To: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>,
openembedded-core <openembedded-core@lists.openembedded.org>,
Yocto Project <yocto@yoctoproject.org>
Subject: OpenEmbeddded Developer meeting Oct 9 after ELCE in Dublin
Date: Sat, 15 Aug 2015 09:23:42 +0200 [thread overview]
Message-ID: <55CEE8FE.6070907@balister.org> (raw)
Just a reminder about the meeting in Dublin after ELCE and the Yocto
Project developer day. Everyone, even if you are not sure you are a
developer, is welcome. The goal of the meeting is to work out future
directions for OpenEmbedded so input from users and developers is welcome.
http://openembedded.org/wiki/OEDEM_2015
Please add your name to the attendee list, even if tentative so we can
plan accordingly.
Thanks,
Philip
next reply other threads:[~2015-08-15 7:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-15 7:23 Philip Balister [this message]
2015-09-08 0:17 ` OpenEmbeddded Developer meeting Oct 9 after ELCE in Dublin Eduardo Silva
2015-09-08 8:31 ` Paul Eggleton
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=55CEE8FE.6070907@balister.org \
--to=philip@balister.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=yocto@yoctoproject.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