[oe-commits] [bitbake] branch master-next updated (ce7325a -> 8421f9a)

[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 ce7325a  fetch2/wget: avoid 'maximum recursion depth' RuntimeErrors when handling 403 codes
 discard 53a12b8  fetch2/npm: Use npm pack to download node modules instead of wget
 discard fcef3b1  toaster: Sync list of fs_types with oe-core
 discard d666036  fixes
 discard 6d5fe23  hashserv: Use separate threads for answering requests and handling them
 discard 9b1ec9b  prserv: Use a memory journal
 discard be369a3  hashserv: Turn off sqlite synchronous mode
 discard b1b5c15  cooker/hashserv: Allow autostarting of a local hash server using BB_HASHSERVE
 discard 35a4685  runqueue: Enable dynamic task adjustment to hash equivalency
 discard e956840  siggen: Add new unitaskhashes data variable which is cached
 discard a223391  runqueue: Improve scenequeue processing logic
 discard 4599242  cache: Add SimpleCache class
 discard 4ed096b  bitbake: hashserv: SQL Optimizations
     add 1dddfe3  toaster: Sync list of fs_types with oe-core
     add e5eda38  fetch2/npm: Use npm pack to download node modules instead of wget
     add 18d4a31  fetch2/wget: avoid 'maximum recursion depth' RuntimeErrors when handling 403 codes
     new 3eec592  bitbake: hashserv: SQL Optimizations
     new 2fef65d  cache: Add SimpleCache class
     new f90e7e7  runqueue: Improve scenequeue processing logic
     new 9e55165  siggen: Add new unitaskhashes data variable which is cached
     new c9c5978  runqueue: Enable dynamic task adjustment to hash equivalency
     new d550ae9  cooker/hashserv: Allow autostarting of a local hash server using BB_HASHSERVE
     new 06a62b6  hashserv: Turn off sqlite synchronous mode
     new 681479b  prserv: Use a memory journal
     new f61bbd4  hashserv: Use separate threads for answering requests and handling them
     new 8421f9a  fixes

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   (ce7325a)
            \
             N -- N -- N   refs/heads/master-next (8421f9a)

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