[oe-commits] [openembedded-core] branch master-next updated (c38f32a -> f11fc16)

[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 c38f32a  oeqa: QEMU_USE_KVM can list machines
 discard d335aab  oeqa: tolerate interrupted select() while waiting for qemu
 discard 47d61a2  dnf: move the entire dnf/rpm4 stack to Python 3
 discard 600e8df  python3: do not hardcode "lib" into site-packages search path
 discard 49cc20b  insane.bbclass: error if file-rdeps not met
 discard 092041b  devtool: open kconfig fragment in binary mode
 discard 3dfd26b  boost: enable more libraries
 discard 602d11d  boost: build context and coroutine on ARM
 discard adf77b8  eudev: restore userspace firmware loading support
 discard 9698821  oeqa/core/loader.py: Do not import underscore modules by default
 discard 98a2592  oeqa: allow persistent image writes in runqemu()
 discard 72ebf8b  oeqa: allow customizing image used by runqemu()
 discard 8365473  oeqa: allow extending qemuparams="..."
     add 2c6eac7  oeqa/core/loader.py: Do not import underscore modules by default
     add d6b139e  eudev: restore userspace firmware loading support
     add 72bec63  devtool: open kconfig fragment in binary mode
     add 90bc7bf  insane.bbclass: error if file-rdeps not met
     add f60d261  python3: do not hardcode "lib" into site-packages search path
     add bedcdc4  dnf: move the entire dnf/rpm4 stack to Python 3
     add 44fe106  oeqa: tolerate interrupted select() while waiting for qemu
     add d5421dd  oeqa: QEMU_USE_KVM can list machines
     new 3f665c4  oeqa: allow extending qemuparams="..."
     new 795ba07  oeqa: allow customizing image used by runqemu()
     new b18f3de  oeqa: allow persistent image writes in runqemu()
     new 188ac24  boost: build context and coroutine on ARM
     new f11fc16  boost: enable more libraries

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   (c38f32a)
            \
             N -- N -- N   refs/heads/master-next (f11fc16)

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 5 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.