[oe-commits] [openembedded-core] branch master-next updated (067af56 -> e0d9588)

git at git.openembedded.org git at git.openembedded.org
Sat Oct 20 16:16:40 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 067af56  Revert "systemd: Remove items that made this machine (qemu) specific"
 discard bb9b405  Revert "systemd: Test revert of patch removal"
 discard f9ec510  valgrind: update from 3.13.0 to 3.14.0
 discard bf5c202  systemd: Test revert of patch removal
 discard 79aae35  volatile-binds: use overlayfs if available
 discard 9e5a837  openssl: do an out-of-tree build
 discard 101dbb1  openssl: fix ptest
 discard 2d794cb  npm: change install directory to upstream default
 discard 536e54f  devtool-source.bbclass: Only create each patch branch once
 discard 2f57887  image_types: Fix a shell syntax error in do_image_ubi
 discard ad5753e  buildtools-tarball: add nativesdk-rpcsvc-proto
 discard 074bd75  tcmode-default: Drop pinning go to 1.9
 discard 393e5e0  go: Upgrade to 1.11.1
 discard 35c5bb4  systemd: add back alternatives for init utitilies
     new cde1682  go: Upgrade to 1.11.1
     new 31e80bc  tcmode-default: Drop pinning go to 1.9
     new d09c1b5  buildtools-tarball: add nativesdk-rpcsvc-proto
     new 51971d6  image_types: Fix a shell syntax error in do_image_ubi
     new b1f66b1  devtool-source.bbclass: Only create each patch branch once
     new 9c73d03  npm: change install directory to upstream default
     new 5f44817  openssl: fix ptest
     new d38597c  openssl: do an out-of-tree build
     new 2a0199c  volatile-binds: use overlayfs if available
     new 9f50b9a  systemd: Test revert of patch removal
     new a717cd4  valgrind: update from 3.13.0 to 3.14.0
     new e0d9588  Revert "systemd: Test revert of patch removal"

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   (067af56)
            \
             N -- N -- N   refs/heads/master-next (e0d9588)

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 12 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/conf/distro/include/maintainers.inc           |  1 +
 meta/conf/layer.conf                               |  1 +
 meta/recipes-core/systemd/systemd-conf.bb          | 51 ++++++++++++++++++++
 ....c-Change-the-default-device-timeout-to-2.patch | 35 --------------
 meta/recipes-core/systemd/systemd_239.bb           | 55 +++++-----------------
 5 files changed, 65 insertions(+), 78 deletions(-)
 create mode 100644 meta/recipes-core/systemd/systemd-conf.bb
 delete mode 100644 meta/recipes-core/systemd/systemd/0001-core-device.c-Change-the-default-device-timeout-to-2.patch

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


More information about the Openembedded-commits mailing list