[oe-commits] [meta-openembedded] branch master-next updated (efbfd23 -> 2ba368c)

[git at git.openembedded.org]

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

  discards  efbfd23   webkit-efl: blacklist, webkit-efl is old and unmaintained fork with security issues
  discards  2b19a8d   gst-ffmpeg: blacklist, not compatible with currently used ffmpeg 3
  discards  9dabc31   mplayer2: blacklist, not compatible with currently used ffmpeg 3
  discards  98a407e   vlc: blacklist, not compatible with currently used ffmpeg 3
  discards  7a845f0   opencv: blacklist, not compatible with currently used ffmpeg 3
  discards  54223e0   linux-yocto-tiny-kexecboot: fix build error (cpio not found)
  discards  1f08d19   libvpx: upgrade to version 1.5.0
  discards  272d936   cppunit: fix loads of host-user-contaminated warnings
  discards  325aaeb   network-manager-applet: update to 1.0.10
  discards  ed35b3c   nginx: make the 1.8.x branch the default
  discards  1838f11   nginx: add stable version 1.8.1 as alternative to the mainline version 1.9.x
  discards  369dcfa   nginx: split parts out of the recipe into nginx.inc
       new  91dedeb   network-manager-applet: update to 1.0.10
       new  456b2c8   cppunit: fix loads of host-user-contaminated warnings
       new  609c79f   libvpx: upgrade to version 1.5.0
       new  c54f464   linux-yocto-tiny-kexecboot: fix build error (cpio not found)
       new  3633f5c   opencv: blacklist, not compatible with currently used ffmpeg 3
       new  f91631d   vlc: blacklist, not compatible with currently used ffmpeg 3
       new  596096e   mplayer2: blacklist, not compatible with currently used ffmpeg 3
       new  9f930b7   gst-ffmpeg: blacklist, not compatible with currently used ffmpeg 3
       new  2ba368c   webkit-efl: blacklist, webkit-efl is old and unmaintained fork with security issues

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

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 "omits" are not gone; other references still
refer to them.  Any revisions marked "discards" 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 "adds" were already present in the repository and have only
been added to this reference.


Summary of changes:
 meta-webserver/recipes-httpd/nginx/nginx.inc       | 137 ---------------------
 meta-webserver/recipes-httpd/nginx/nginx_1.8.1.bb  |   4 -
 meta-webserver/recipes-httpd/nginx/nginx_1.9.11.bb | 137 ++++++++++++++++++++-
 3 files changed, 133 insertions(+), 145 deletions(-)
 delete mode 100644 meta-webserver/recipes-httpd/nginx/nginx.inc
 delete mode 100644 meta-webserver/recipes-httpd/nginx/nginx_1.8.1.bb

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