[oe-commits] [openembedded-core] branch master-next updated (7877e00 -> 219085d)

[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 7877e00  xserver-xorg: Fix build errors with clang
 discard b6a6c05  grub: Enhance Waddress-of-packed-member patch to cover x86_64 testcase
 discard 4a912c5  uboot-extlinux-config.bbclass: add missing variable dependencies
 discard b380407  gdk-pixbuf: export XDG_DATA_DIRS in wrappers
 discard 54a8dde  selftest: add tests for virgl GL acceleration
     new b74021b  selftest: add tests for virgl GL acceleration
     new 38aa5f5  gdk-pixbuf: export XDG_DATA_DIRS in wrappers
     new b17483a  uboot-extlinux-config.bbclass: add missing variable dependencies
     new 6e11d36  grub: Enhance Waddress-of-packed-member patch to cover x86_64 testcase
     new 219085d  xserver-xorg: Fix build errors with clang

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   (7877e00)
            \
             N -- N -- N   refs/heads/master-next (219085d)

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:
 meta-selftest/lib/oeqa/runtime/cases/virgl.py | 5 -----
 1 file changed, 5 deletions(-)

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