[oe-commits] [bitbake] branch master-next updated (484e509 -> 08b8a49)

[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 484e509  persist_data.py: Immediately get exclusive lock in __setitem__
 discard 82f0a64  fetch2/git: _revision_key: collapse adjacent slashes
 discard abeb68d  fetch2: do not suffix srcrev cache key with PN
 discard d058fe4  tests/utils: add tests for bb.utils.get_referenced_vars
 discard 9f481b5  bb.utils: add get_referenced_vars
 discard a149cfc  lib: amend code to use proper singleton comparisons where possible
 discard 3685b36  lib: remove unused imports
 discard 7ffd1b5  fixup
 discard 6d16eb5  fix2
 discard bf028e6  bitbake: siggen: Cache unihash values to avoid cache lookup
 discard 13b6ad8  bitbake: siggen: Optimise get_unihash handling [fixme commit msg]
 discard f2856ae  tests/fetch: Allow wget upgrade tests to run against a local server
 discard a7db5b9  runqueue: Possible tid handling optimisation
     add 4367692  lib: remove unused imports
     add b809a68  lib: amend code to use proper singleton comparisons where possible
     add 076eb54  bb.utils: add get_referenced_vars
     add 346e74e  tests/utils: add tests for bb.utils.get_referenced_vars
     add 6c938e6  fetch2: do not suffix srcrev cache key with PN
     add 425e21c  fetch2/git: _revision_key: collapse adjacent slashes
     add feb43e7  persist_data.py: Immediately get exclusive lock in __setitem__
     new e1104b5  runqueue: Possible tid handling optimisation
     new 5569b5b  tests/fetch: Allow wget upgrade tests to run against a local server
     new 545f806  bitbake: siggen: Optimise get_unihash handling [fixme commit msg]
     new 7824edf  bitbake: siggen: Cache unihash values to avoid cache lookup
     new 9e8afd7  fix2
     new 08b8a49  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   (484e509)
            \
             N -- N -- N   refs/heads/master-next (08b8a49)

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 6 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:

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