From: akuster808 <akuster808@gmail.com>
To: openembedded-devel@lists.openembedded.org,
Martin Jansa <martin.jansa@gmail.com>,
Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: When will the meta-openembedded have a dizzy branch, please ?
Date: Fri, 10 Oct 2014 12:45:44 -0700 [thread overview]
Message-ID: <54383768.3020705@gmail.com> (raw)
In-Reply-To: <54381ED3.60805@balister.org>
On 10/10/2014 11:00 AM, Philip Balister wrote:
> We'll need volunteers to maintain.
You can put me down as one if it helps.
- Armin
Also a lot of people are headed to
> ELCE next week, so we might be slow getting this organized.
>
> Philip
>
> On 10/10/2014 01:00 PM, Robert Yang wrote:
>> Hello,
>>
>> When will the meta-openembedded have a dizzy branch, please ?
>>
next prev parent reply other threads:[~2014-10-10 19:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 17:00 When will the meta-openembedded have a dizzy branch, please ? Robert Yang
2014-10-10 18:00 ` Philip Balister
2014-10-10 19:14 ` Otavio Salvador
2014-10-14 14:55 ` Cliff Brake
2014-10-14 17:48 ` Otavio Salvador
2014-10-10 19:45 ` akuster808 [this message]
2014-10-10 21:44 ` Martin Jansa
2014-10-11 15:53 ` Otavio Salvador
2014-10-11 16:22 ` akuster808
2014-10-11 18:00 ` Otavio Salvador
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=54383768.3020705@gmail.com \
--to=akuster808@gmail.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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.