From: akuster808 <akuster808@gmail.com>
To: "otavio@ossystems.com.br >> Otavio Salvador" <otavio@ossystems.com.br>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
openembedded-devel@lists.openembedded.org
Subject: Re: When will the meta-openembedded have a dizzy branch, please ?
Date: Sat, 11 Oct 2014 09:22:34 -0700 [thread overview]
Message-ID: <5439594A.1050800@gmail.com> (raw)
In-Reply-To: <CAP9ODKrGx=QsmXSJuTNBgzjN-PgDGs3=rtqpLu7inBdUEzfP3g@mail.gmail.com>
On 10/11/2014 08:53 AM, Otavio Salvador wrote:
> On Fri, Oct 10, 2014 at 6:44 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
>> On Sat, Oct 11, 2014 at 01:00:53AM +0800, Robert Yang wrote:
>>> Hello,
>>>
>>> When will the meta-openembedded have a dizzy branch, please ?
>>
>> It would be nice to get at least some of QA issues fixed before we
>> branch. Currently we have more than 438 issues.
>
> I agree we ought to fix the QA issues but this shouldn't delay the
> branching; we can backport those fixes once proved fine on master.
>
>> But other than that, it's almost ready (thanks Otavio + Armin for
>> stepping up to maintain it), please send the READMEs update again when
>> you can, so that I can create the branch together with right READMEs.
>
> Armin, do you want to do the patch and add my name? or should I do and
> add yours? Two patches seems overkill :)
I can do it.
What email do you want me to use?
- Armin
next prev parent reply other threads:[~2014-10-11 16:22 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
2014-10-10 21:44 ` Martin Jansa
2014-10-11 15:53 ` Otavio Salvador
2014-10-11 16:22 ` akuster808 [this message]
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=5439594A.1050800@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--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.