[oe-commits] [openembedded-core] branch master-next updated (f51d0a2 -> 4209cd2)

[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 f51d0a2  populate_sdk_ext: Use prebuilt uninative tarball
 discard ae4206f  kernel-yocto: ensure that only a single defconfig is processed
 discard a815823  kernel-yocto: Stop the build if defconfig is missing
 discard 37485bc  kernel-yocto: ensure sccs variable is set when using KBUILD_DEFCONFIG
 discard ac98c3b  linux-yocto/4.12: update to v4.12.16
 discard 196d066  linux-yocto/4.9: update to v4.9.65
 discard ec234be  linux-yocto/4.12: iwlwifi calltrace fixes and configuration warning cleanups
 discard 19ab5f0  linux-yocto/4.9: update to v4.9.61
 discard b666e5d  mkelfimage: Remove un-needed recipe
 discard a368d51  oeqa/qemu: remove elf image type
 discard c071648  image_types: Remove ELF type
 discard ffcda6d  XX runqemu: dump pagetypeinfo if qemu fails
 discard 9f96b1a  qemu: use upstream swtpm support
 discard 55fad90  i2c-tools: upgrade to 4.0
     new 05aec19  qemu: use upstream swtpm support
     new e24198f  image_types: Remove ELF type
     new 26fdd53  oeqa/qemu: remove elf image type
     new 3e09a4a  mkelfimage: Remove un-needed recipe
     new fd35f2a  linux-yocto/4.9: update to v4.9.61
     new 16ac772  linux-yocto/4.12: iwlwifi calltrace fixes and configuration warning cleanups
     new 6f7033b  linux-yocto/4.9: update to v4.9.65
     new ca97e27  linux-yocto/4.12: update to v4.12.16
     new 254d96f  kernel-yocto: ensure sccs variable is set when using KBUILD_DEFCONFIG
     new 1200ff4  kernel-yocto: Stop the build if defconfig is missing
     new 598e6c2  kernel-yocto: ensure that only a single defconfig is processed
     new 1bee69c  populate_sdk_ext: Use prebuilt uninative tarball
     new 4209cd2  XX runqemu: dump pagetypeinfo if qemu fails

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   (f51d0a2)
            \
             N -- N -- N   refs/heads/master-next (4209cd2)

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 13 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/i2c-tools/files/Module.mk    | 72 ++++++++++++++++++++++
 .../{i2c-tools_4.0.bb => i2c-tools_3.1.2.bb}       | 14 +++--
 2 files changed, 81 insertions(+), 5 deletions(-)
 create mode 100644 meta/recipes-devtools/i2c-tools/files/Module.mk
 rename meta/recipes-devtools/i2c-tools/{i2c-tools_4.0.bb => i2c-tools_3.1.2.bb} (64%)

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