[oe-commits] [openembedded-core] branch master-next updated (58a4f86 -> b9b27d6)

[git at git.openembedded.org]

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 58a4f86  scripts/oe-build-perf-test: Use python3 from the environment
 discard 1172226  buildstats: Replace 'is' with '==' in python condition check expression
 discard 3dfeaca  libjpeg-turbo: Build reproducibly
 discard c4c56b6  nasm: Add debug-prefix-map option
 discard 9003dfd  Revert "go: Reset unneeded GOARCH variables for native recipe"
 discard 66b9e55  goarch: Remove target specific dependencies
 discard 5d91173  cronie:fix SRC_URI path
 discard 483ba5b  bluez5: disable debug output in ptests
 discard c71ae6e  bluez: update 5.50 -> 5.52
 discard c64eff9  kbd: avoid vlock conflict with busybox
 discard 2a04e6f  reproducible_build_simple: inherit podfix
 discard 731c18c  podfix: class to remove Pod::Man versions from manpages
 discard 17ecfb0  sstatesig: Optimise
 discard aa94a3e  conf/machine/x86-base: use wic instead of live
 discard e4e3e39  runqemu: handle tap device creation failure properly
 discard 2e56e79  runqemu: log parameters correctly within testimage
 discard a496cb1  oeqa: qemu: ensure we print runqemu output in the event of failure
 discard 24de126  oeqa: qemu: fix width of top output in host dump
 discard 50b40dd  oeqa: qemu: ensure that host dump commands can be run properly
 discard 2a238c6  HACK: signing: Add extra test debug
 discard bac4222  HACK: Enable saving of packages
     add 3f6dcf6  oeqa: qemu: ensure that host dump commands can be run properly
     add 07da998  oeqa: qemu: fix width of top output in host dump
     add c1def38  oeqa: qemu: ensure we print runqemu output in the event of failure
     add ca64a3d  runqemu: log parameters correctly within testimage
     add 47e40fd  runqemu: handle tap device creation failure properly
     add 18d8e5a  podfix: class to remove Pod::Man versions from manpages
     add 5dc43ed  reproducible_build_simple: inherit podfix
     add 0863670  kbd: avoid vlock conflict with busybox
     add 1a31a31  bluez: update 5.50 -> 5.52
     add 78221af  bluez5: disable debug output in ptests
     add 06ce571  cronie:fix SRC_URI path
     add 83eebf5  goarch: Remove target specific dependencies
     add 18b9096  Revert "go: Reset unneeded GOARCH variables for native recipe"
     add ad5c914  nasm: Add debug-prefix-map option
     add 9119a88  libjpeg-turbo: Build reproducibly
     add c3cb6bc  buildstats: Replace 'is' with '==' in python condition check expression
     add 04e4e93  conf/machine/x86-base: use wic instead of live
     add de98cfe  sstatesig: Optimise get_taskhash for hashequiv
     add 81ee68f  scripts/oe-build-perf-test: Use python3 from the environment
     new e5910e4  HACK: Enable saving of packages
     new b9b27d6  HACK: signing: Add extra test debug

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   (58a4f86)
            \
             N -- N -- N   refs/heads/master-next (b9b27d6)

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 2 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:

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.