[oe-commits] [meta-openembedded] branch master-next updated (2703a39 -> 1453c21)

[git at git.openembedded.org]

This is an automated email from the git hooks/post-receive script.

khem pushed a change to branch master-next
in repository meta-openembedded.

 discard 2703a39  libnfc: Fix build with musl
 discard a692cc7  polkit: fix CVE-2019-6133
 discard 7bb24a1  python-obd: Uprade from 0.7.0 to 0.7.1
 discard 1a8ba5c  python-ldap: update to 3.2.0
 discard 053d057  rp-pppoe: update to 3.13
 discard b7d28c7  opensaf: update to 5.19.03
 discard e1bfde7  libowfat: update to 0.32
     new 7ada285  opensaf: update to 5.19.03
     new 949af7e  rp-pppoe: update to 3.13
     new ac2fd7c  python-ldap: update to 3.2.0
     new 808bedb  python-obd: Uprade from 0.7.0 to 0.7.1
     new 2ba3c34  polkit: fix CVE-2019-6133
     new 1453c21  libnfc: Fix build with musl

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   (2703a39)
            \
             N -- N -- N   refs/heads/master-next (1453c21)

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 6 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:
 .../recipes-support/ncp/{libowfat_0.32.bb => libowfat_0.31.bb}      | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
 rename meta-networking/recipes-support/ncp/{libowfat_0.32.bb => libowfat_0.31.bb} (80%)

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