[oe-commits] [openembedded-core] branch master-next updated (6cfec08 -> 306250d)

[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 6cfec08  sstate: Implement hash equivalence sstate
 discard 13c6337  classes/sstate: Handle unihash in hash check
 discard 17ce92c  kernel.bbclass: Fix incorrect deploying of fitimage.initramfs
 discard 1ba2a43  update-alternatives.bbclass: Stabilize iteration order
 discard 9bc051f  u-boot.inc: Support menuconfig for u-boot
 discard 530ea83  classes/buildhistory: avoid git diff churn by sorting more dictionaries
 discard fe12f84  iw: fix parsing of WEP keys
 discard 6650926  arch-armv4.inc, arch-armv5.inc: Do not tie generating thumb ISA to -march
 discard 36d625e  oeqa/utils/qemurunner: set timeout to 60s for run_serial
 discard 86b864c  netbase: add entry to /etc/hosts according to /etc/hostname
 discard 648a89a  python-native: fix one do_populate_sysroot warning
 discard 7fce513  python/python3: use cc_basename to replace CC for checking compiler
     add 8197d0f  oeqa/utils/qemurunner: set timeout to 60s for run_serial
     add 49bc3ea  arch-armv4.inc, arch-armv5.inc: Do not tie generating thumb ISA to -march
     add 6de9eb7  iw: fix parsing of WEP keys
     add 031d708  classes/buildhistory: avoid git diff churn by sorting more dictionaries
     add 11278e3  u-boot.inc: Support menuconfig for u-boot
     add 3262202  update-alternatives.bbclass: Stabilize iteration order
     add 0f87f85  kernel.bbclass: Fix incorrect deploying of fitimage.initramfs
     new 96383ef  python/python3: use cc_basename to replace CC for checking compiler
     new cf99475  python-native: fix one do_populate_sysroot warning
     new bccf10f  netbase: add entry to /etc/hosts according to /etc/hostname
     new 45cf414  classes/sstate: Handle unihash in hash check
     new 306250d  sstate: Implement hash equivalence sstate

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   (6cfec08)
            \
             N -- N -- N   refs/heads/master-next (306250d)

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.