[oe-commits] [openembedded-core] branch master-next updated (b394d96 -> b0e137e)

[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 b394d96  mesa: Upgrade 18.1.3 -> 18.1.7
 discard fc4d35a  linux-firmware: Update to feb25f3e revision
 discard 0030f85  go-dep: Update 0.4.1 -> 0.5.0
 discard 1b4ec44  openssl: do not tweak so names, use PRIVATE_LIBS instead
 discard a8a975d  openssh: depend on libressl
 discard bfaa840  ca-certificates: update to 20180409
 discard 3b8bbd0  libressl: add a recipe to support openssh
 discard 93d5a0a  openssl: update to 1.1.1
 discard 9bf8e6c  cryptodev-tests: port to openssl 1.1
 discard fc9de52  openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version
 discard 0809a54  package.bbclass: warn if perms conf file does not exist
 discard 5f7b1f1  openssh: update from 7.7p1 to 7.8p1
 discard 46b2bb1  gdb: Seprate out gold and dwp into a variable
 discard c5a52e2  tcf-agent: Disable non-building features on riscv64
 discard f5e55f9  packagegroup-core-tools-testapps: Exclude gst-examples on riscv64
 discard d68f019  glibc-locale: Enable riscv64 and riscv32 in BINARY_LOCALE_ARCHES supported architectures
 discard 9768759  libc-package: Add risc-v specific options to cross-localedef invocation
 discard 0b9d4e5  boost: Fix invalid const in atomic builtins
 discard 4364ee1  add todo to worker
 discard 26ba792  recipes: Update git.gnome.org addresses after upstream changes
     new dec56f2  add todo to worker
     new 92e44d8  boost: Fix invalid const in atomic builtins
     new 2756568  libc-package: Add risc-v specific options to cross-localedef invocation
     new 2b1ee2b  glibc-locale: Enable riscv64 and riscv32 in BINARY_LOCALE_ARCHES supported architectures
     new ec1e165  packagegroup-core-tools-testapps: Exclude gst-examples on riscv64
     new d9d742c  tcf-agent: Disable non-building features on riscv64
     new 8d831ca  gdb: Seprate out gold and dwp into a variable
     new 25da5ab  openssh: update from 7.7p1 to 7.8p1
     new 3d48210  package.bbclass: warn if perms conf file does not exist
     new e12710b  openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version
     new 47d76ca  cryptodev-tests: port to openssl 1.1
     new b445ab8  openssl: update to 1.1.1
     new 7c9eda8  libressl: add a recipe to support openssh
     new 0ca8fc8  ca-certificates: update to 20180409
     new 8fa2318  openssh: depend on libressl
     new 6650111  openssl: do not tweak so names, use PRIVATE_LIBS instead
     new 9d80d99  go-dep: Update 0.4.1 -> 0.5.0
     new 7069a83  linux-firmware: Update to feb25f3e revision
     new de0307b  mesa: Upgrade 18.1.3 -> 18.1.7
     new b0e137e  recipes: Update git.gnome.org addresses after upstream changes

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   (b394d96)
            \
             N -- N -- N   refs/heads/master-next (b0e137e)

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 20 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.