[oe-commits] [openembedded-core] branch master-next updated (7cb1841 -> eeae586)

[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 openembedded-core.

 discard 7cb1841  oeqa/bbtests: Tweak test
 discard 59f6fed  core-image-sato-sdk-ptest: Reduce image padding size due to bootimg 4GB limit
 discard 38f09e3  cve maint native fixup
 discard 07303cb  package: Force rebuild for testing
 discard 091ace5  Revert "pigz: Add debug for autobuilder errors"
 discard c6530e4  pigz: Add debug for autobuilder errors
 discard 404370a  meta: Improve handling of VIRTUAL-RUNTIME variables
 discard 725094e  util-linux:upgrade 2.33.2 -> 2.34
 discard 532de4a  i2c-tools: Add alternative for i2ctransfer
 discard 3070d06  libdrm: update to 2.4.99
 discard b1207c0  go.bbclass: separate the ptest logic to go-ptest class
 discard b228523  cve-check: Update unpatched CVE matching
 discard 228af62  cve-update-db: Use NVD CPE data to populate PRODUCTS table
 discard 4ccee09  cve-check: Depends on cve-update-db-native
 discard 983212c  defaultsetup.conf: enable select init manager
     add 4078da9  cve-check: Depends on cve-update-db-native
     add f7676e9  cve-update-db: Use NVD CPE data to populate PRODUCTS table
     add bc0195b  cve-check: Update unpatched CVE matching
     add 099a2a2  go.bbclass: separate the ptest logic to go-ptest class
     add 09e7f60  libdrm: update to 2.4.99
     add 0325aae  i2c-tools: Add alternative for i2ctransfer
     add c868543  util-linux:upgrade 2.33.2 -> 2.34
     add 9f974dd  core-image-sato-sdk-ptest: Reduce image padding size due to bootimg 4GB limit
     add 78fcea7  oeqa/bbtests: Tweak test bitbake output pattern matching
     new 568a037  defaultsetup.conf: enable select init manager
     new c306799  meta: Improve handling of VIRTUAL-RUNTIME variables
     new 5b7aa1b  pigz: Add debug for autobuilder errors
     new a3cdaae  Revert "pigz: Add debug for autobuilder errors"
     new eeae586  package: Force rebuild for testing

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   (7cb1841)
            \
             N -- N -- N   refs/heads/master-next (eeae586)

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