[oe-commits] [openembedded-core] branch master-next updated (a5149c7 -> e2fa6bc)

git at git.openembedded.org git at git.openembedded.org
Sun Oct 14 15:04:59 UTC 2018


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 a5149c7  nasm: fix CVE-2018-10016
 discard 94e6703  glib.inc: drop duplicate locale-base-fr-fr runtime dependency
 discard 962cca2  local.conf.sample.extended: add another warning to comment about GLIBC_GENERATE_LOCALES
 discard 4fb7db4  glibc: Do not use thumb1 ISA on armv6
 discard ae73d6b  util-linux: fix alternatives setting for switch-root
     new de01490  glibc: Do not use thumb1 ISA on armv6
     new 3814c85  local.conf.sample.extended: add another warning to comment about GLIBC_GENERATE_LOCALES
     new 7535797  glib.inc: drop duplicate locale-base-fr-fr runtime dependency
     new e2fa6bc  nasm: fix CVE-2018-10016

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

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 4 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-core/util-linux/util-linux.inc | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

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


More information about the Openembedded-commits mailing list