[oe-commits] [openembedded-core] branch master-next updated (daf3081 -> 5fa7ea7)
git at git.openembedded.org
git at git.openembedded.org
Sun Aug 19 15:35:56 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 daf3081 kernel-devsrc: restructure for out of tree (and on target) module builds
discard fa19a2d openssl: update 1.1.0h -> 1.1.0i
discard 220a71f openssl: update 1.0.2o -> 1.0.2p
discard ed27cea vala: refresh patch
discard 7a85df4 glibc: re-package for libnss-db
discard 1343ec0 oe-selftest: quick hack to test
add 13cf502 glibc: re-package for libnss-db
add dfbbff3 vala: refresh patch
add ff3db93 openssl: update 1.0.2o -> 1.0.2p
add 0d19cae openssl: update 1.1.0h -> 1.1.0i
add 007ef1f kernel-devsrc: restructure for out of tree (and on target) module builds
new 5fa7ea7 oe-selftest: quick hack to test
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 (daf3081)
\
N -- N -- N refs/heads/master-next (5fa7ea7)
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 1 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.
More information about the Openembedded-commits
mailing list