[oe-commits] [bitbake] branch master-next updated (6fe06d0 -> 64407bc)

[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 6fe06d0  runqueue: Fix task migration problems
 discard 55b2201  bitbake: hashserv: Add more threads
 discard 0b1831e  bitbake: hashserve: Log I/O waits and SQL time
 discard 0b88592  bitbake: hashserv: Add request statistics
     add 4cf5bb7  tests/fetch: Resolve fetch error in bitbake-selftest
     new 70796a8  bitbake: hashserv: Add request statistics
     new 148fc1e  bitbake: hashserve: Log I/O waits and SQL time
     new c9a9c3d  bitbake: hashserv: Add more threads
     new 64407bc  runqueue: Fix task migration problems

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   (6fe06d0)
            \
             N -- N -- N   refs/heads/master-next (64407bc)

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/tests/fetch.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

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