From: brian avery <brian.avery@intel.com>
To: toaster@yoctoproject.org
Cc: brian avery <brian.avery@intel.com>
Subject: [PATCH 0/3] [Morty] toaster:update fixtures for morty release
Date: Thu, 13 Oct 2016 18:12:24 -0700 [thread overview]
Message-ID: <cover.1476407209.git.brian.avery@intel.com> (raw)
This changes the fixtures for toaster in Morty so that
1) We only allow the morty branch for new projects
2) we default to morty when making a new project.
This release we do not support building older releases due to
the Python 2.7 -> Python 3 change Morty represents.
This patch set updates both the poky and oe-core fixtures.
Note: this only applies to the Morty branch and should *not* be applied to
master.
-bavery
The following changes since commit 1a95d4a0701b87ae3674239a01aabe38a0123585:
bitbake: bitbake-user-manual: Changed BB_SETSCENE_VERIFY_FUNCTION name (2016-10-13 23:29:25 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib bavery/toaster/mortyFixtures
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/toaster/mortyFixtures
brian avery (3):
toaster: Update oe-core fixture for Morty release
toaster: Update poky fixture for Morty release
toaster: Update default release to Morty
bitbake/lib/toaster/orm/fixtures/oe-core.xml | 16 ++++++++--------
bitbake/lib/toaster/orm/fixtures/poky.xml | 12 ++++++------
bitbake/lib/toaster/orm/fixtures/settings.xml | 2 +-
3 files changed, 15 insertions(+), 15 deletions(-)
--
1.9.1
next reply other threads:[~2016-10-14 1:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 1:12 brian avery [this message]
2016-10-14 1:12 ` [PATCH 1/3] toaster: Update oe-core fixture for Morty release brian avery
2016-10-14 10:36 ` Michael Wood
2016-10-14 1:12 ` [PATCH 2/3] toaster: Update poky " brian avery
2016-10-14 1:12 ` [PATCH 3/3] toaster: Update default release to Morty brian avery
2016-10-14 15:29 ` Michael Wood
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.1476407209.git.brian.avery@intel.com \
--to=brian.avery@intel.com \
--cc=toaster@yoctoproject.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.