From: brian avery <avery.brian@gmail.com>
To: bitbake-devel@lists.openembedded.org
Cc: brian avery <brian.avery@intel.com>
Subject: [PATCH 0/3] toaster: add master branch back into new project options
Date: Wed, 9 Nov 2016 19:52:31 -0800 [thread overview]
Message-ID: <cover.1478749786.git.brian.avery@intel.com> (raw)
This patch adds master to the oe and poky fixtures so that a new project can be
based on morty or the master branch.
It also has an fix for lsupdates to support the layers in fixtures definition.
-Brian
an intel employee
The following changes since commit 065310e77ab4c8c914c53ff43d5e601ebf9468b5:
toaster: settings set ALLOWED_HOSTS to * in debug mode (2016-11-09 16:28:17 -0800)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib bavery/submit/toaster/mw-masterproj-11-2016
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/submit/toaster/mw-masterproj-11-2016
Michael Wood (3):
toaster: settings fixture Set default release to master
toaster: orm/fixtures Add the master release and correct morty release
toaster: layerindex updater Take into account layers being predefined
lib/toaster/orm/fixtures/oe-core.xml | 23 ++++++-
lib/toaster/orm/fixtures/poky.xml | 82 ++++++++++++++++++++++--
lib/toaster/orm/fixtures/settings.xml | 2 +-
lib/toaster/orm/management/commands/lsupdates.py | 60 ++++++-----------
4 files changed, 116 insertions(+), 51 deletions(-)
--
1.9.1
next reply other threads:[~2016-11-10 3:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 3:52 brian avery [this message]
2016-11-10 3:52 ` [PATCH 1/3] toaster: settings fixture Set default release to master brian avery
2016-11-10 3:52 ` [PATCH 2/3] toaster: orm/fixtures Add the master release and correct morty release brian avery
2016-11-10 3:52 ` [PATCH 3/3] toaster: layerindex updater Take into account layers being predefined brian avery
2016-11-22 21:19 ` [PATCH 0/3] toaster: add master branch back into new project options Brian Avery
2016-11-23 12:19 ` Richard Purdie
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.1478749786.git.brian.avery@intel.com \
--to=avery.brian@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=brian.avery@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.