From: brian avery <brian.avery@intel.com>
To: toaster@yoctoproject.org
Cc: brian avery <brian.avery@intel.com>
Subject: [PATCH 0/3] toaster: add master branch back in to releases
Date: Mon, 31 Oct 2016 14:22:35 -0700 [thread overview]
Message-ID: <cover.1477948776.git.brian.avery@intel.com> (raw)
For the morty release we removed master so it couldn't be chosen from the
"new project" settings. Now that the bitbake version of 1.32 has been fixed
for Morty, we can add the maaster release back into the fixtures.
This is being done for poky and oe-core. They will both default to master
on the master branch.
-Brian
an intel employee
The following changes since commit 003b053498aea91fdb8c5418d0d8bbda7b23dbc0:
boost: fix the SRC_URI to point to an actual release, and not a master snapshot (2016-10-31 14:23:12 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib bavery/toaster/addbackMasterRelease
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/toaster/addbackMasterRelease
brian avery (3):
toaster: Update oe-core fixture for Morty plus master release
toaster: Update oe-core fixture for Morty plus master release
toaster: Update default release to master
lib/toaster/orm/fixtures/oe-core.xml | 12 ++++++++++++
lib/toaster/orm/fixtures/poky.xml | 13 +++++++++++++
lib/toaster/orm/fixtures/settings.xml | 2 +-
3 files changed, 26 insertions(+), 1 deletion(-)
--
1.9.1
next reply other threads:[~2016-10-31 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 21:22 brian avery [this message]
2016-10-31 21:22 ` [PATCH 1/3] toaster: Update oe-core fixture for Morty plus master release brian avery
2016-10-31 21:22 ` [PATCH 2/3] " brian avery
2016-11-02 12:02 ` Michael Wood
2016-11-02 14:47 ` Brian Avery
2016-10-31 21:22 ` [PATCH 3/3] toaster: Update default release to master brian avery
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.1477948776.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.