[oe-commits] [bitbake] branch master-next updated (f413159 -> 7ffd1b5)

[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 f413159  fixup
 discard f6458af  fix2
 discard 04b3a9e  bitbake: siggen: Cache unihash values to avoid cache lookup
 discard cdb4cfb  bitbake: siggen: Optimise get_unihash handling [fixme commit msg]
 discard ce162b6  bitbake: runqueue: Reorder task migration changes
     new 13b6ad8  bitbake: siggen: Optimise get_unihash handling [fixme commit msg]
     new bf028e6  bitbake: siggen: Cache unihash values to avoid cache lookup
     new 6d16eb5  fix2
     new 7ffd1b5  fixup

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

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 4 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/runqueue.py | 49 ++++++++++++++++++-------------------------------
 1 file changed, 18 insertions(+), 31 deletions(-)

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