[oe-commits] [openembedded-core] branch master-next updated (a1400bc -> 0f28028)

git at git.openembedded.org git at git.openembedded.org
Fri Feb 15 23:17:30 UTC 2019

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 a1400bc  icecc-env: don't raise error when icecc not installed
 discard 3d3d6b5  nfs-utils: build tools with target compiler
 discard 2a8d7b1  oeqa/manual/bsp-hw.json: add non-IA tests
 discard 64f7baa  linux-firmware: Bump to 710963f revision
 discard 7e6b227  bmap-tools: update from 3.4 to 3.5
     new 9956bb1  linux-firmware: Bump to 710963f revision
     new e21ce74  oeqa/manual/bsp-hw.json: add non-IA tests
     new 9a8e525  nfs-utils: build tools with target compiler
     new 0f28028  icecc-env: don't raise error when icecc not installed

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   (a1400bc)
             N -- N -- N   refs/heads/master-next (0f28028)

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:
 .../bmap-tools/{bmap-tools_3.5.bb => bmap-tools_3.4.bb}          | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)
 rename meta/recipes-support/bmap-tools/{bmap-tools_3.5.bb => bmap-tools_3.4.bb} (74%)

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

More information about the Openembedded-commits mailing list