[oe-commits] [bitbake] branch master-next updated (d0c8264 -> 66f1b76)

[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 d0c8264  cooker: Split recipes to parse amongst threads ahead of time
 discard c8d4c7e  cooker: Remove Feeder() since its no longer needed with moderm multiprocessing
 discard 71ce6e0  tests.data: Add underscore+numeric in overrides datastore test
 discard 8bf587a  bitbake: hashserv: Add hash equivalence reference server
 discard 8684df6  bitbake: persist_data: Fix Locking Protocol Error
 discard 9c351db  data/siggen: Switch md5 -> sha256
 discard 76914b3  codeparser: Switch to sha256 from md5
     add 93cd156  bitbake: persist_data: Fix Locking Protocol Error
     add 1bb2ad0  bitbake: hashserv: Add hash equivalence reference server
     add 08c314e  tests.data: Add underscore+numeric in overrides datastore test
     add b2d39fc  cooker: Remove Feeder() since its no longer needed with moderm multiprocessing
     add ae79868  cooker: Split recipes to parse amongst threads ahead of time
     add 4bed7a9  codeparser: Switch to sha256 from md5
     add 66f1b76  data/siggen: Switch md5 -> sha256

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   (d0c8264)
            \
             N -- N -- N   refs/heads/master-next (66f1b76)

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.

No new revisions were added by this update.

Summary of changes:

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