[oe-commits] [bitbake] branch master-next updated (c18a26a -> ec5871f)

git at git.openembedded.org git at git.openembedded.org
Thu Sep 19 19:32:11 UTC 2019


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

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

 discard c18a26a  bitbake: runqueue: Fix task migration problems
     add 048bd05  bitbake-layers: show-recipes: Show recipes only
     add 8c38d95  bitbake-layers: show-recipes: Select recipes from selected layer
     add 87796e5  bitbake-layers: show-recipes: Enable bare output
     add be0b78c  fetch2/git: add git-lfs toggle option
     add 45cb73e  runqueue: validate_hashes(): currentcount should be a number
     add 797354d  utils: Add ionice option to prunedir
     new ec5871f  runqueue: Fix task migration problems

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   (c18a26a)
            \
             N -- N -- N   refs/heads/master-next (ec5871f)

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 1 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:
 lib/bb/fetch2/git.py  | 18 +++++++++++-------
 lib/bb/runqueue.py    |  6 +++---
 lib/bb/utils.py       | 11 +++++++----
 lib/bblayers/query.py | 39 ++++++++++++++++++++++++---------------
 4 files changed, 45 insertions(+), 29 deletions(-)

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


More information about the Openembedded-commits mailing list