[oe-commits] [meta-openembedded] branch master-next updated (5210b20 -> e3291a9)

git at git.openembedded.org git at git.openembedded.org
Thu Jun 16 20:43:11 UTC 2016


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

  discards  5210b20   poco: update to 1.7.3
  discards  302f6bb   iperf: resolve issues with gcc6
  discards  24ed3fa   chrony: Versatile implementation of NTP
  discards  6ee0008   v4lutils: Update to latest upstream
  discards  71dfe77   libgphoto2: correct compatibility issues with libjpeg-turbo-1.5.0
  discards  f1cc456   python-pyephem_3.7.6.0.bb: Add new recipe.
  discards  869ee3e   gtk-engines: Move from oe-core
  discards  b02eb65   curlpp: fix build with gcc-6 and remove blacklist
  discards  73c6d89   wireshark: update to 2.0.4
  discards  16d6722   ntp: Security fixes via Upgrade to 4.2.8p8
  discards  097f911   crda, lftp, curlpp: blacklist, fails to build with gcc-6
  discards  b2dbabd   openconnect: fix do_compile failure
  discards  e6db74b   openconnect: add dependency to fix Makefile.am
      adds  f0756d1   crda, lftp, curlpp: blacklist, fails to build with gcc-6
      adds  13db3c6   ntp: Security fixes via Upgrade to 4.2.8p8
      adds  f316c4a   wireshark: update to 2.0.4
      adds  5c8efcc   curlpp: fix build with gcc-6 and remove blacklist
      adds  9cd117a   chrony: Versatile implementation of NTP
       new  539de56   openconnect: add dependency to fix Makefile.am
       new  bf5805a   openconnect: fix do_compile failure
       new  01442db   gtk-engines: Move from oe-core
       new  79120dd   python-pyephem_3.7.6.0.bb: Add new recipe.
       new  b8d8198   libgphoto2: correct compatibility issues with libjpeg-turbo-1.5.0
       new  e3717e0   v4lutils: Update to latest upstream
       new  4112352   iperf: resolve issues with gcc6
       new  e3291a9   poco: update to 1.7.3

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   (5210b20)
            \
             N -- N -- N   refs/heads/master-next (e3291a9)

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 8 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:

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


More information about the Openembedded-commits mailing list