[oe-commits] [openembedded-core] branch master-next updated (d2130d2 -> 1f14275)

[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 d2130d2  busybox: Backport patches to support removal of __NR_clock_gettime
 discard 676af1a  gdb: Upgrade to 9.1 release
 discard f4c1d16  musl: Update to latest tip
 discard 2a902e2  ruby: upgrade 2.6.5 -> 2.7.0
 discard c43b16b  wic: Honor APPEND
 discard 728e904  python3-pip: upgrade 19.3.1 -> 20.0.2
 discard 24e5c54  ffmpeg: add PACKAGECONFIG support for x265
 discard e3b9e48  strace: Update to 5.5
 discard ac524f8  perf: Correct the substitution of python shebangs
 discard ef1c156  glibc-testsuite: Exclude this recipe from world builds
 discard 4b926b9  glibc-testsuite: Remove the do_install task
 discard 3c6b87e  make: 4.2.1 -> 4.3
     new c715d51  glibc-testsuite: Remove the do_install task
     new 06ae420  glibc-testsuite: Exclude this recipe from world builds
     new a286a07  strace: Update to 5.5
     new 6a92209  ffmpeg: add PACKAGECONFIG support for x265
     new 392c4aa  python3-pip: upgrade 19.3.1 -> 20.0.2
     new 7f6ef47  wic: Honor APPEND
     new 51fba6a  ruby: upgrade 2.6.5 -> 2.7.0
     new 2b72f3b  busybox: Backport patches to support removal of __NR_clock_gettime
     new acdd1d4  musl: Update to latest tip
     new 1f14275  gdb: Upgrade to 9.1 release

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   (d2130d2)
            \
             N -- N -- N   refs/heads/master-next (1f14275)

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 10 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:
 ...all-wrappers-around-clock_gettime-closes-.patch | 13 +++-
 ...unsv-Use-64-prefix-syscall-if-we-have-to.patch} | 33 +++++-----
 meta/recipes-core/busybox/busybox_1.31.1.bb        |  3 +-
 meta/recipes-devtools/make/make.inc                |  4 +-
 ...1-glob-Do-not-assume-glibc-glob-internals.patch | 70 ++++++++++++++++++++++
 ...2-glob-Do-not-assume-glibc-glob-internals.patch | 38 ++++++++++++
 meta/recipes-devtools/make/make_4.2.1.bb           | 12 ++++
 meta/recipes-devtools/make/make_4.3.bb             | 10 ----
 meta/recipes-kernel/perf/perf.bb                   |  7 ++-
 9 files changed, 158 insertions(+), 32 deletions(-)
 copy meta/recipes-core/busybox/busybox/{0001-time-Use-64-prefix-syscall-if-we-have-to.patch => 0003-runsv-Use-64-prefix-syscall-if-we-have-to.patch} (60%)
 create mode 100644 meta/recipes-devtools/make/make/0001-glob-Do-not-assume-glibc-glob-internals.patch
 create mode 100644 meta/recipes-devtools/make/make/0002-glob-Do-not-assume-glibc-glob-internals.patch
 create mode 100644 meta/recipes-devtools/make/make_4.2.1.bb
 delete mode 100644 meta/recipes-devtools/make/make_4.3.bb

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