From: Martin Jansa <martin.jansa@gmail.com>
To: Trevor Woerner <twoerner@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: next bitbake world run and updates
Date: Wed, 30 Dec 2015 18:32:04 +0100 [thread overview]
Message-ID: <20151230173204.GG2263@jama> (raw)
In-Reply-To: <56840B6A.3080001@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
On Wed, Dec 30, 2015 at 11:50:50AM -0500, Trevor Woerner wrote:
> Hi Martin,
>
> I'm hoping my nodejs_4.2.3.bb makes it into your next "State of bitbake
> world" run and passes this time. When do you think your next "bitbake
> world" will occur? I ask because since sending my v4 patches for
> nodejs_4.2.3, node-v4.2.4 has been released.
It's running for last 2 days already, it should be finished in next 2
days. Your recent v4 is included (at least for qemux86*, qemuarm was
already running when I've updated master-next and jansa/master
branches).
Previous "christmas" build was wasted, because of server issues in the
middle of the build. As bonus I had time to go through cumulated logs
and fix few more issues around for current build.
> Do I send the list a patch of the delta between 4.2.3 and 4.2.4? Or do I
> update my entire patchset and send a v5?
I also hope that last 4.2.3 build will be OK and your change merged in
master, so I would prefer separate patch just for 4.2.4.
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2015-12-30 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 16:50 next bitbake world run and updates Trevor Woerner
2015-12-30 17:32 ` Martin Jansa [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=20151230173204.GG2263@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=twoerner@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox