[oe-commits] [bitbake] branch master-next updated (1ebdbbf -> d59bcf1)

[git at git.openembedded.org]

rpurdie pushed a change to branch master-next
in repository bitbake.

  discards  1ebdbbf   COW.py: fix sample codes
  discards  35bbc7b   toaster: layerindex updater Take into account layers being predefined
  discards  be88863   toaster: orm/fixtures Add the master release and correct morty release
  discards  9e8620d   toaster: settings fixture Set default release to master
  discards  0af0eec   taskdata.py: improve handling of depends/rdepends
  discards  ab20503   data_smart.py: don't reorder internal bitbake variables when calculating hash
  discards  ddb38f9   data_smart: Default to expansion for getVar/getVarFlags
  discards  dff5e1a   data: Drop deprecated old style bitbake API
  discards  c081059   lib/bb: Don't use deprecated bb.data.getVar/setVar API
  discards  4055276   fetch2: npm: conditionally hide NPM_LOCKDOWN / NPM_SHRINKWRAP warnings
  discards  a2156f7   WIP bitbake-worker/cooker: more logging to aid debugging
      adds  cefb8c9   fetch2: npm: conditionally hide NPM_LOCKDOWN / NPM_SHRINKWRAP warnings
      adds  ff7892f   lib/bb: Don't use deprecated bb.data.getVar/setVar API
      adds  1825604   data: Drop deprecated old style bitbake API
      adds  caf5bb9   data_smart: Default to expansion for getVar/getVarFlags
      adds  3511d46   data_smart.py: don't reorder internal bitbake variables when calculating hash
      adds  063d255   taskdata.py: improve handling of depends/rdepends
      adds  115cee1   toaster: settings fixture Set default release to master
      adds  c83ab92   toaster: orm/fixtures Add the master release and correct morty release
      adds  f981b68   toaster: layerindex updater Take into account layers being predefined
      adds  d140f0e   COW.py: fix sample codes
       new  d59bcf1   WIP bitbake-worker/cooker: more logging to aid debugging

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   (1ebdbbf)
            \
             N -- N -- N   refs/heads/master-next (d59bcf1)

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 1 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.