[oe-commits] [meta-openembedded] branch master-next updated (e4ff50a -> d3f57eb)

[git at git.openembedded.org]

This is an automated email from the git hooks/post-receive script.

khem pushed a change to branch master-next
in repository meta-openembedded.

 discard e4ff50a  ftgl: initial add 2.1.3-rc5
 discard 9b73fcc  faenza-icon-theme: Fix multilib fetch
 discard cc69c39  physfs: Fix multilib install
 discard 3d41b11  menulibre: Fix multilib fetch
 discard 24d08f7  vncx11: Fix dev package do_rootfs failure
 discard a05ffed  gerbera: Update to 1.3.0
 discard eff2dcb  libupnp: Upgrade to 1.8.4
     new 3d7f68c  libupnp: Upgrade to 1.8.4
     new e0fe1b0  gerbera: Update to 1.3.0
     new 5b5fae3  vncx11: Fix dev package do_rootfs failure
     new 47e16ad  menulibre: Fix multilib fetch
     new f75c5e0  physfs: Fix multilib install
     new 61ee9cc  faenza-icon-theme: Fix multilib fetch
     new d3f57eb  ftgl: initial add 2.1.3-rc5

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   (e4ff50a)
            \
             N -- N -- N   refs/heads/master-next (d3f57eb)

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 7 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-multimedia/recipes-connectivity/libupnp/libupnp_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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