[oe-commits] [openembedded-core] branch master-next updated (b754cb5 -> 802bb1b)
git at git.openembedded.org
git at git.openembedded.org
Tue Feb 28 11:28:10 UTC 2017
This is an automated email from the git hooks/post-receive script.
rpurdie pushed a change to branch master-next
in repository openembedded-core.
discard b754cb5 recipes: Make use of the new bb.utils.filter() function
discard def57a6 sanity: Require bitbake 1.33.2
discard f25079a ovmf: increase path length limit
discard 979e002 acpica: fix compilation with musl
discard 212e4e6 kernel, license, sstate, rootfs.py: Remove deploy directory README
discard dc2f179 ovmf: remove BGRT patch
discard ead206a ovmf: build image which enrolls standard keys
discard 18cfa4c runqemu: support UEFI with OVMF firmware
discard 318c876 runqemu: also accept -image suffix for rootfs parameter
discard b1caa1a runqemu: fix undefined variable reference in check_arg_path()
discard 80fee5a ovmf_git.bb: enable Secure Boot
discard b0677a0 ovmf_git.bb: enable parallel compilation
discard cedda0e ovmf: deploy firmware in image directory
discard 582f1d9 ovmf: explicitly depend on nasm-native
discard c9d04f4 ovmf: move from meta-luv to OE-core
new d656298 acpica: fix compilation with musl
new 49cdce8 ovmf: move from meta-luv to OE-core
new 92198bd ovmf: explicitly depend on nasm-native
new 6f84653 ovmf: deploy firmware in image directory
new be30760 ovmf_git.bb: enable parallel compilation
new d493f0b ovmf_git.bb: enable Secure Boot
new 3f11e4c runqemu: fix undefined variable reference in check_arg_path()
new ca0fad3 runqemu: also accept -image suffix for rootfs parameter
new b91fc08 runqemu: support UEFI with OVMF firmware
new 1913ace ovmf: build image which enrolls standard keys
new 240e96e ovmf: remove BGRT patch
new ea296ab ovmf: increase path length limit
new 71e9e88 kernel, license, sstate, rootfs.py: Remove deploy directory README
new 6db2633 sanity: Require bitbake 1.33.2
new 802bb1b recipes: Make use of the new bb.utils.filter() function
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (b754cb5)
\
N -- N -- N refs/heads/master-next (802bb1b)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 15 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../VfrCompile-increase-path-length-limit.patch | 33 ++++++++++++++++++++++
meta/recipes-core/ovmf/ovmf_git.bb | 6 +---
2 files changed, 34 insertions(+), 5 deletions(-)
create mode 100644 meta/recipes-core/ovmf/ovmf/VfrCompile-increase-path-length-limit.patch
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
More information about the Openembedded-commits
mailing list