[oe-commits] [openembedded-core] branch master-next updated (319145e -> 610cb3d)

[git at git.openembedded.org]

rpurdie pushed a change to branch master-next
in repository openembedded-core.

  discards  319145e   systemd-compat-units: pkg_postinst() does not work
  discards  ff1ea43   XXX prelink: fix on older host gcc
  discards  13ef5c9   Revert "local.conf.sample: Disable prelink by default"
  discards  4e982aa   prelink: Move to latest version of prelink
      adds  ecc8d34   sanity: Require bitbake 1.31.1 for multi-config changes
       new  a328b9a   prelink: Move to latest version of prelink
       new  c24b5b5   Revert "local.conf.sample: Disable prelink by default"
       new  395e8fe   XXX prelink: fix on older host gcc
       new  525cbb5   systemd-compat-units: pkg_postinst() does not work
       new  610cb3d   systemd-compat-units: Only enable for systemd in DISTRO_FEATURES

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   (319145e)
            \
             N -- N -- N   refs/heads/master-next (610cb3d)

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 "omits" are not gone; other references still
refer to them.  Any revisions marked "discards" 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 "adds" were already present in the repository and have only
been added to this reference.


Summary of changes:
 meta/conf/sanity.conf                             | 2 +-
 meta/recipes-core/systemd/systemd-compat-units.bb | 4 +++-
 2 files changed, 4 insertions(+), 2 deletions(-)

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