[yocto-security] [OE-core CVE] branch master-next updated. uninative-2.7-128-gbdc62e2

cve-notice at lists.openembedded.org cve-notice at lists.openembedded.org
Sat Oct 19 15:19:35 PDT 2019


This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "".

The branch, master-next has been updated
  discards  a7d8fdfef7588ba02ee19f251e9d9c97a06d933c (commit)
  discards  7f9e2497d65032d1bbd7eea8a0e82976895f7b40 (commit)
  discards  26decb3fbcd5e4f60445b419b8812469e82b22c8 (commit)
       via  bdc62e2845fc242cf0778623690fadcb8da731d4 (commit)
       via  3b788da31af6296a0404ed6080aef17708d61303 (commit)

This update added new revisions after undoing existing revisions.  That is
to say, the old revision is not a strict subset of the new revision.  This
situation occurs when you --force push a change and generate a repository
containing something like this:

 * -- * -- B -- O -- O -- O (a7d8fdfef7588ba02ee19f251e9d9c97a06d933c)
            \
             N -- N -- N (bdc62e2845fc242cf0778623690fadcb8da731d4)

When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
-----------------------------------------------------------------------

Summary of changes:


hooks/post-receive
-- 



More information about the yocto-security mailing list