From: Joshua Lock <joshuagloe@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] Python3 runqemu
Date: Mon, 5 Sep 2016 14:59:08 +0100 [thread overview]
Message-ID: <cover.1473083836.git.joshua.g.lock@intel.com> (raw)
This small series against master-next (as the python3 runqemu hasn't made it to
master yet) fixes the new runqemu for a workflow of mine where I build on a
headless machine and copy images locally to test them with runqemu.
The following changes since commit e0f246cefb8b6642e0df98067ade06833e83c1f8:
gobject-introspection: set GI_SCANNER_DISABLE_CACHE for native (2016-09-05 11:59:01 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib joshuagl/runqemu
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=joshuagl/runqemu
Joshua Lock (4):
runqemu: fix typos
runqemu: use glob rather than calling out to ls
runqemu: assume artefacts are relative to *.qemuboot.conf
runqemu: get NATIVE dirs from env when in source OE build dir
scripts/runqemu | 44 ++++++++++++++++++++++++++++++++++++++------
1 file changed, 38 insertions(+), 6 deletions(-)
--
2.7.4
next reply other threads:[~2016-09-05 13:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 13:59 Joshua Lock [this message]
2016-09-05 13:59 ` [PATCH 1/4] runqemu: fix typos Joshua Lock
2016-09-05 13:59 ` [PATCH 2/4] runqemu: use glob rather than calling out to ls Joshua Lock
2016-09-05 14:51 ` Robert Yang
2016-09-05 15:51 ` Joshua Lock
2016-09-05 13:59 ` [PATCH 3/4] runqemu: assume artefacts are relative to *.qemuboot.conf Joshua Lock
2016-09-05 13:59 ` [PATCH 4/4] runqemu: get NATIVE dirs from env when in source OE build dir Joshua Lock
2016-09-05 14:47 ` Robert Yang
2016-09-05 15:49 ` Joshua Lock
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=cover.1473083836.git.joshua.g.lock@intel.com \
--to=joshuagloe@gmail.com \
--cc=openembedded-core@lists.openembedded.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.