[oe-commits] [openembedded-core] branch master-next updated (f2702cb -> 3c77e34)

[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 f2702cb  maintainers: update Intel owners
 discard 07e4f02  mesa: add lost Upstream-Status
 discard e0835db  bitbake.conf/testimage: Add in compatiblity hacks
 discard e1ddffb  subversion: Update HOMEPAGE
 discard d2201dc  mktemp: remove
 discard 4c62d6b  mesa: Update 18.1.1 -> 18.1.2
 discard d92f2a9  linux-firmware: upgrade to d114732 revision
 discard ff65720  findutils: make -delete honour the -ignore_readdir_race option
 discard e04063b  xkbcomp: update to 1.4.2
 discard 521a395  xf86-video-vmware: update to 13.3.0
 discard c650cfb  xf86-input-evdev: update 2.10.6
 discard d28587f  xkeyboard-config: update to 2.24
 discard eb52ac3  subversion: 1.9.7 -> 1.10.0
 discard f91560c  lttng-modules: upgrade 2.10.5 -> 2.10.6
 discard 0c30c9d  image/testimage: Rework auto image test execution
     new b34d44f  image/testimage: Rework auto image test execution
     new 3ba2701  lttng-modules: upgrade 2.10.5 -> 2.10.6
     new 5bb4798  subversion: 1.9.7 -> 1.10.0
     new 64a3e9c  xkeyboard-config: update to 2.24
     new 61f72d4  xf86-input-evdev: update 2.10.6
     new cdc00f9  xf86-video-vmware: update to 13.3.0
     new ed26f8f  xkbcomp: update to 1.4.2
     new f0808ee  findutils: make -delete honour the -ignore_readdir_race option
     new 6be8744  linux-firmware: upgrade to d114732 revision
     new 0cfc748  mesa: Update 18.1.1 -> 18.1.2
     new 59a825c  mktemp: remove
     new 5da1b9c  subversion: Update HOMEPAGE
     new 309a029  bitbake.conf/testimage: Add in compatiblity hacks
     new 4972faf  mesa: add lost Upstream-Status
     new b503b1f  maintainers: update Intel owners
     new 147f5a6  oe/types: Allow boolean to accept an existing boolean
     new 3c77e34  gcc-target: Enable fp arch extention when fpu is available

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   (f2702cb)
            \
             N -- N -- N   refs/heads/master-next (3c77e34)

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 17 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/classes/testimage.bbclass                                      | 2 +-
 meta/classes/testsdk.bbclass                                        | 2 +-
 meta/lib/oe/types.py                                                | 2 ++
 meta/recipes-devtools/gcc/gcc-target.inc                            | 6 +++---
 .../0001-find-make-delete-honour-the-ignore_readdir_race-opti.patch | 2 +-
 5 files changed, 8 insertions(+), 6 deletions(-)

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