[oe-commits] [bitbake] branch master-next updated (0f0b0c2 -> 5d62c5c)

[git at git.openembedded.org]

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

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

 discard 0f0b0c2  tests: Add initial scenario based test for runqueue
 discard 28d035b  runqueue: Fix
 discard f4080ce  runqueue: fixes
 discard ed88cd3  fixup5
 discard 92ee87e  fixup4
 discard 824bc85  fixes3
 discard 3ec44e8  fixes2
 discard c4701e4  fixes
 discard d12ba01  runqueue: Complete the merge of scenequeue and normal task execution
 discard 84e7961  runqueue: Alter setscenewhitelist handling
 discard 69a1c43  runqueue: Merge the queues and execute setscene and normal tasks in parallel
 discard 65adff2  runqueue: Clarify scenequeue_covered vs. tasks_covered
 discard a11b5ca  runqueue: Further scheduler buildable tasks cleanup
 discard 94d9444  runqueue: Remove pointless variable
 discard 20952f1  runqueue: Code simplification
 discard e5236b6  runqueue: Tweak comments and debug code
 discard fbda198  runqueue: Simplify scenequeue unskippable calculation
 discard 275e795  runqueue: Add covered_tasks (or 'collated_deps') to scenequeue data
 discard f512ee5  event/runqueue: Drop StampUpdate event, its pointless/unused
 discard 3a3435e  runqueue: Fold remains of the scenequeue setup into RunQueueExecute
 discard 6c1322d  runqueue: Simplify _execute_runqueue logic
 discard 08bcb98  runqueue: Remove RunQueueExecuteScenequeue and RunQueueExecuteTasks
 discard f6c7de2  runqueue: Merge scenequeue and real task queue code together
 discard 710a686  runqueue: Merge stats handling together for setscene/real tasks
 discard 882711d  runqueue: Uniquely namespace the scenequeue functions
 discard da740d7  runqueue: Factor out the process_setscene_whitelist checks
 discard 3ebc894  runqueue: Remove unused function parameter
 discard c335e23  runqueue: Move scenequeue data generation to a separate function
 discard 7216ec5  runqueue: Remove now uneeded code
 discard 6e3aae8  runqueue: Drop unused BB_SETSCENE_VERIFY_FUNCTION2
     new d41708b  runqueue: Tweak buildable variable handling in scheduler
     new 10ee145  runqueue: Drop unused BB_SETSCENE_VERIFY_FUNCTION2
     new 4c7620d  runqueue: Remove now uneeded code
     new 06ab079  runqueue: Move scenequeue data generation to a separate function
     new 12c79ec  runqueue: Remove unused function parameter
     new ebb7ca5  runqueue: Factor out the process_setscene_whitelist checks
     new 5db3757  runqueue: Uniquely namespace the scenequeue functions
     new 9124d1e  runqueue: Merge stats handling together for setscene/real tasks
     new 05d4945  runqueue: Merge scenequeue and real task queue code together
     new fa14400  runqueue: Fix counter/task updating glitch
     new 776e868  runqueue: Remove RunQueueExecuteScenequeue and RunQueueExecuteTasks
     new 67a0dda  runqueue: Simplify _execute_runqueue logic
     new 89d697d  runqueue: Fold remains of the scenequeue setup into RunQueueExecute
     new 58e7f53  event/runqueue: Drop StampUpdate event, its pointless/unused
     new 357ac45  runqueue: Add covered_tasks (or 'collated_deps') to scenequeue data
     new 83d0349  runqueue: Simplify scenequeue unskippable calculation
     new a0b8ad9  runqueue: Tweak comments and debug code
     new e4e8d1e  runqueue: Code simplification
     new df05eea  runqueue: Remove pointless variable
     new 6232535  runqueue: Further scheduler buildable tasks cleanup
     new 2045fd5  runqueue: Clarify scenequeue_covered vs. tasks_covered
     new 1dabd98  runqueue: Merge the queues and execute setscene and normal tasks in parallel
     new dbfdb05  runqueue: Alter setscenewhitelist handling
     new 4589ad2  runqueue: Complete the merge of scenequeue and normal task execution
     new 67c9fdb  siggen: Fix default handler
     new 5d62c5c  tests: Add initial scenario based test for runqueue

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   (0f0b0c2)
            \
             N -- N -- N   refs/heads/master-next (5d62c5c)

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 26 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/siggen.py | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

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