[oe-commits] [openembedded-core] branch master-next updated (acd4ffc -> f8a527a)
git at git.openembedded.org
git at git.openembedded.org
Tue Jun 27 09:39:18 UTC 2017
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 acd4ffc meta: Add/fix missing Upstream-Status to patches
discard 0646018 meta: Fix malformed Upstream-Status tags
discard 5bddcf8 lttng-modules: update to 2.9.3
discard 468447b lttng-tools: update to 2.9.5
discard 3a44b4e lttng-ust: update to 2.9.1
discard 9743a60 runqemu: drop RPC ports
add 6e1aaf8 meta: Fix malformed Upstream-Status tags
add 563cab8 meta: Add/fix missing Upstream-Status to patches
new c616a73 runqemu: drop RPC ports
new 39f4368 lttng-ust: update to 2.9.1
new eb64685 lttng-tools: update to 2.9.5
new f8a527a lttng-modules: update to 2.9.3
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 (acd4ffc)
\
N -- N -- N refs/heads/master-next (f8a527a)
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:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
More information about the Openembedded-commits
mailing list