[oe-commits] [openembedded-core] branch master-next updated (93ce40f -> f98f8a9)

[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 93ce40f  selftest/wic.py: vda -> sda
 discard 46298b9  oe-selftest: test wic sparse_copy API
 discard 217e417  ptest-runner: Upgrade to minor version 2.0.2
 discard a8dbe3f  qemux86-directdisk.wks: vda -> sda
 discard fc5484b  runqemu: use self.rootfs to replace self.nfs_dir
 discard 60a977c  python2/3: Remove building host path from packages
     new c875645  runqemu: use self.rootfs to replace self.nfs_dir
     new 5d958a4  qemux86-directdisk.wks: vda -> sda
     new e612efd  ptest-runner: Upgrade to minor version 2.0.2
     new 1210279  oe-selftest: test wic sparse_copy API
     new f98f8a9  selftest/wic.py: vda -> sda

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   (93ce40f)
            \
             N -- N -- N   refs/heads/master-next (f98f8a9)

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/recipes-devtools/python/python3_3.5.2.bb | 8 +-------
 meta/recipes-devtools/python/python_2.7.13.bb | 6 ------
 2 files changed, 1 insertion(+), 13 deletions(-)

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