[oe-commits] [bitbake] branch master-next updated (9adbdc4 -> afda8a0)

[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 9adbdc4  hashserv: Don't daemonize server process
 discard 51bb984  siggen: Fix attribute error when hashserver fails
 discard fa719e9  hashserve: Add missing import
 discard 7111ffb  cookerdata: Add mc conffiles hashes to cache hash
 discard 28839be  siggen: Remove full path from unitaskhashes keys
 discard bc7d9ef  runqueue: Small performance optimisation
 discard 595171d  runqueue: Save unihashes more frequently
 discard 9b59fa5  siggen fix
 discard 6f9bb79  siggen/runqueue: Fix sig issues
 discard 7cb6660  hashequiv experiment
 discard 9bc5732  tests/data: Test combinations of _append together with override
 discard e07b839  tests/fetch: add test case for git-lfs handling
 discard 3706fac  fetch2/git: refactor check for git-lfs command
 discard cfb5b32  siggen: fix
 discard 78660c1  test fixup
 discard ec5871f  runqueue: Fix task migration problems
     add 33cf917  fetch2/git: refactor check for git-lfs command
     add a7cf4fc  tests/fetch: add test case for git-lfs handling
     add f31f35e  tests/data: Test combinations of _append together with override
     add c74481a  cookerdata: Add mc conffiles hashes to cache hash
     add 31a5111  hashserve: Add missing import
     add 9fb8626  siggen: Fix attribute error when hashserver fails
     add 7c82967  hashserv: Don't daemonize server process
     new 7a30443  runqueue: Fix task migration problems
     new 240903f  test fixup
     new 1c8fb5c  siggen: fix
     new 407cd51  hashequiv experiment
     new 8e85a2c  siggen/runqueue: Fix sig issues
     new b34d66c  siggen fix
     new a79997c  runqueue: Save unihashes more frequently
     new 0090469  runqueue: Small performance optimisation
     new afda8a0  siggen: Remove full path from unitaskhashes keys

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   (9adbdc4)
            \
             N -- N -- N   refs/heads/master-next (afda8a0)

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 9 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.