[oe-commits] [openembedded-core] branch master-next updated (3507ad6 -> ce4a536)

[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 3507ad6  package_ipk: Remove pointless comment to trigger rebuild
 discard fd380ff  HACK: Enable saving of packages
 discard ec183d2  oeqa/selftest/sstatetests: Ensure we don't use hashequiv for sstatesigs tests
 discard d8cff2c  sanity: Add check for tar older than 1.28
 discard 1cb3637  oe-selftest: extend virgl gtk test to also check the SDL option
     add 0fdc43d  sanity: Add check for tar older than 1.28
     add 6af5594  oeqa/selftest/sstatetests: Ensure we don't use hashequiv for sstatesigs tests
     add 6dd59df  package_ipk: Remove pointless comment to trigger rebuild
     new 5eedb55  oe-selftest: extend virgl gtk test to also check the SDL option
     new ce4a536  HACK: Enable saving of packages

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   (3507ad6)
            \
             N -- N -- N   refs/heads/master-next (ce4a536)

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.