[oe-commits] [openembedded-core] branch master-next updated (2b2f77b -> d0d55ad)

[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 2b2f77b  libxml2: Make it compatible with externalsrc
 discard e81ed7b  lsof: Make it compatible with externalsrc
 discard 45eb2ca  acl: Make it compatible with externalsrc
 discard 8d2c32a  cmake.bbclass: allow cmake to find hosttools
 discard 3a2eb99  cmake.bbclass: move CMAKE_NO_SYSTEM_FROM_IMPORTED to toolchain.cmake
 discard 967bc4c  cmake.bbclass: search both sysroot-native and host for native packages
 discard 92ca2f3  cmake.bbclass: use CMAKE_SYSTEM_LIBRARY_PATH instead of CMAKE_LIBRARY_PATH
     new 8a12bb7  acl: Make it compatible with externalsrc
     new 51f9a0e  lsof: Make it compatible with externalsrc
     new d0d55ad  libxml2: Make it compatible with externalsrc

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   (2b2f77b)
            \
             N -- N -- N   refs/heads/master-next (d0d55ad)

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 3 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/cmake.bbclass | 24 +++++++++---------------
 1 file changed, 9 insertions(+), 15 deletions(-)

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