From: akuster808 <akuster808@gmail.com>
To: Philip Balister <philip@balister.org>,
akuster <akuster@mvista.com>, Jeff Osier-Mixon <jefro@jefro.net>,
Yocto Project <yocto@yoctoproject.org>,
yocto-announce@yoctoproject.org
Subject: Re: Embedded Linux Conference, YP DevDay, and OEDAM
Date: Wed, 24 Feb 2016 13:31:56 -0800 [thread overview]
Message-ID: <56CE214C.7040002@gmail.com> (raw)
In-Reply-To: <56CDE328.4090708@balister.org>
On 2/24/16 9:06 AM, Philip Balister wrote:
> On 02/23/2016 11:53 AM, akuster808 wrote:
>>
>> On 01/27/2016 01:49 PM, Philip Balister wrote:
>>> On 01/27/2016 07:49 PM, akuster wrote:
>>>>
>>>> On 01/27/2016 10:15 AM, Jeff Osier-Mixon wrote:
>>>>> If you are planning to attend the Embedded Linux Conference in San
>>>>> Diego this April, I wanted to let you know about the Yocto Project
>>>>> Developer Day that the team is planning. This will be similar to
>>>>> previous DevDays, with hands-on training in both introductory and
>>>>> advanced tracks. The day will happen just after ELC, on April 7 at the
>>>>> Marriott in downtown San Diego, just across from the ELC venue. We'll
>>>>> have more details posted later this week.
>>>>>
>>>>> The project is also a sponsor for the event and we will have a booth.
>>>>> If you have something cool that you have been working on and would
>>>>> like to show it off in the booth during the conference, let me know
>>>>> and we'll see what we can do to make some space for your project.
>>>> I will be bring at least one demo. Not sure if its cool.
>>>>
>>>>> For those also in the OpenEmbedded community, there will be an OE
>>>>> developer's meeting and working session on Friday, April 8. This is a
>>>>> working session for OE members (not an educational session, sorry!)
>>>>> and space is limited, so if you plan to attend, please let me know so
>>>>> I can plan space accordingly.
>>>> I will be there. I take it there will be a wiki sigh up like before?
>>> Yep, I'm on the road, but will copy the last OE developer meeting to
>>> start to page. If you do not have a wiki account go ahead and make on.
>> Is there an OEDAM page yet?
> There is now. Needs work still.
>
> http://openembedded.org/wiki/OEDAM_2016
>
>>> Accounts need to be approved by a human now, the spammers were getting
>>> bad again :(
>> Submitted a login request a month ago and no email or response.
>>
> Email notifications have been funny, but your account is there. Let me
> know if you are still having problems.
nope. works now.
thanks
Armin
>
> Philip
>
>> I am not a bot.
>>
>> - Armin
>>> Philip
>>>
>>>
>>>
>>>> - armin
>>>>> thanks!
>>>>>
prev parent reply other threads:[~2016-02-24 21:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 18:15 Embedded Linux Conference, YP DevDay, and OEDAM Jeff Osier-Mixon
2016-01-27 18:49 ` akuster
2016-01-27 21:49 ` Philip Balister
2016-02-23 16:53 ` akuster808
2016-02-23 17:13 ` Paul Eggleton
2016-02-24 17:06 ` Philip Balister
2016-02-24 21:31 ` akuster808 [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=56CE214C.7040002@gmail.com \
--to=akuster808@gmail.com \
--cc=akuster@mvista.com \
--cc=jefro@jefro.net \
--cc=philip@balister.org \
--cc=yocto-announce@yoctoproject.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 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.