[oe-commits] [bitbake] branch master-next updated (d22f410 -> 49bea82)

git at git.openembedded.org git at git.openembedded.org
Mon May 9 22:49:54 UTC 2016


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

  discards  d22f410   runqueue: Fix missing fakeworker under dry run
  discards  0c0ba92   lib/bb/utils.py: Fix explode_dep_versions2() determinism issue
  discards  41ac2d4   bin, toaster: Fix print and exception syntax
  discards  f0c0125   tests: assertEquals -> assertEqual
  discards  62c981e   bitbake: Update logger.warn() -> logger.warning()
      adds  676a5f5   bitbake: Update logger.warn() -> logger.warning()
      adds  b60261b   tests: assertEquals -> assertEqual
      adds  58304fc   bin, toaster: Fix print and exception syntax
      adds  0737e00   lib/bb/utils.py: Fix explode_dep_versions2() determinism issue
      adds  49bea82   runqueue: Fix missing fakeworker under dry run

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   (d22f410)
            \
             N -- N -- N   refs/heads/master-next (49bea82)

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.

No new revisions were added by this update.

Summary of changes:
 bin/bitbake-layers               |  2 +-
 lib/bb/fetch2/__init__.py        | 16 ++++++++--------
 lib/bb/ui/buildinfohelper.py     |  6 +++---
 lib/bb/ui/knotty.py              |  2 +-
 lib/toaster/bldcontrol/models.py |  8 ++++----
 5 files changed, 17 insertions(+), 17 deletions(-)

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


More information about the Openembedded-commits mailing list