[oe-commits] [bitbake] branch master-next updated (2e5a52c -> 9c351db)

[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 2e5a52c  runqueue: Pass unique hash to hash validate
 discard 25f0e24  runqueue: Pass unique hash to task
 discard 172b41b  runqueue: Track task unique hash
 discard 89e730b  siggen: Split out task unique hash
 discard bf9efd2  data/siggen: Switch md5 -> sha256
 discard 12500dc  codeparser: Switch to sha256 from md5
     add d0065b3  siggen: Split out task unique hash
     add 1ecc47f  runqueue: Track task unique hash
     add aab80b0  runqueue: Pass unique hash to task
     add 9a529bb  runqueue: Pass unique hash to hash validate
     new 76914b3  codeparser: Switch to sha256 from md5
     new 9c351db  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   (2e5a52c)
            \
             N -- N -- N   refs/heads/master-next (9c351db)

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