[oe-commits] [openembedded-core] branch master-next updated (33a8cb9 -> 4ebc7e2)

[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 33a8cb9  oeqa: reproducible: Do two clean builds
 discard 7b3e8cc  ltp: move from python 2.x to python 3.x
 discard 1e24d96  yocto-check-layer: Allow any case for README file detection
 discard 912d3c0  bind: fix build with python3 PACKAGECONFIG enabled
 discard 42121ed  qemu: bump linux-yocto preferred version to 5.2
 discard f43836d  devsrc: update arm64 scripts/prepare for kernels 5.3+
 discard 9cad1f2  perf: v5.3+ build fixes
 discard 846e022  perf: change dependencies on python to python3
 discard 388293d  kernel-devsrc: remove python2 dependency
 discard 11da23f  bluez5: fix build against libc-headers 5.2+
 discard dc4012f  linux-yocto: introduce 5.2 recipes
 discard eb0c32b  linux-libc-headers: update to v5.2 headers
     new cee2847  bluez5: fix build against libc-headers 5.2+
     new b2ce7e8  kernel-devsrc: remove python2 dependency
     new 43df9bf  perf: change dependencies on python to python3
     new 5f43410  perf: v5.3+ build fixes
     new 1feac36  devsrc: update arm64 scripts/prepare for kernels 5.3+
     new 2449a7e  bind: fix build with python3 PACKAGECONFIG enabled
     new 903dca8  yocto-check-layer: Allow any case for README file detection
     new 847f759  ltp: move from python 2.x to python 3.x
     new 4ebc7e2  oeqa: reproducible: Do two clean builds

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   (33a8cb9)
            \
             N -- N -- N   refs/heads/master-next (4ebc7e2)

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 9 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:
 meta/conf/distro/include/tcmode-default.inc        |  2 +-
 meta/conf/machine/include/x86-base.inc             |  2 +-
 meta/conf/machine/qemuarmv5.conf                   |  2 +-
 ...api-asm-ptrace.h-should-not-depend-on-uap.patch | 62 ++++++++++++++++++++++
 ...bc-headers_5.2.bb => linux-libc-headers_5.0.bb} |  5 +-
 meta/recipes-kernel/linux/linux-yocto-rt_5.2.bb    | 44 ---------------
 meta/recipes-kernel/linux/linux-yocto-tiny_5.2.bb  | 32 -----------
 meta/recipes-kernel/linux/linux-yocto_5.2.bb       | 54 -------------------
 8 files changed, 68 insertions(+), 135 deletions(-)
 create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-arm64-sve-uapi-asm-ptrace.h-should-not-depend-on-uap.patch
 rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_5.2.bb => linux-libc-headers_5.0.bb} (75%)
 delete mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_5.2.bb
 delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_5.2.bb
 delete mode 100644 meta/recipes-kernel/linux/linux-yocto_5.2.bb

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