[oe-commits] [meta-openembedded] branch master-next updated (0c2cf2b -> 50a3814)

[git at git.openembedded.org]

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

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

 discard 0c2cf2b  stunnel: Add HOMEPAGE info into recipe file.
 discard 4a80c78  sgpio: Add HOMEPAGE info into recipe file.
 discard 1967a60  orbit2: Add HOMEPAGE info into recipe file.
 discard af7a589  numactl: Add HOMEPAGE info into recipe file.
 discard 6ee647a  mozjs: Add HOMEPAGE info into recipe file.
 discard 1c9a3ca  mailcap: Add HOMEPAGE info into recipe file.
 discard 6bd7e99  libtdb: Add HOMEPAGE info into recipe file.
 discard e6d0a72  libnih: Add HOMEPAGE info into recipe file.
 discard 4b9bb40  ceres-solver: add new recipe
 discard 6599b7c  drbd-utils: remove 0001-drbd-8.4.4-drbd-tools-only-rmmod-if-DRBD-is-a-module.patch
 discard b19921c  gnome-keyring: Resolve conflict with gcr 3 and gold linking error
 discard b8d43bc  libndp: Add HOMEPAGE info into recipe file.
 discard 95b6a13  fbset: Add HOMEPAGE info into recipe file.
 discard c7470e2  daemontools: Add HOMEPAGE info into recipe file.
 discard c0ffb6c  liblockfile: Add HOMEPAGE info into recipe file.
 discard 412f5f3  libjs-sizzle: Add HOMEPAGE info into recipe file.
 discard 0e3df70  gerbera: clean recipe
 discard 66cbee7  libupnp: Add recipe for version 1.8.2
     new a18db12  libupnp: Add recipe for version 1.8.2
     new 90be7f5  gerbera: clean recipe
     new 62655bc  libjs-sizzle: Add HOMEPAGE info into recipe file.
     new 6c0f9c2  liblockfile: Add HOMEPAGE info into recipe file.
     new 87d004b  daemontools: Add HOMEPAGE info into recipe file.
     new 346b2a5  fbset: Add HOMEPAGE info into recipe file.
     new 2fdb314  libndp: Add HOMEPAGE info into recipe file.
     new a96fc97  gnome-keyring: Resolve conflict with gcr 3 and gold linking error
     new 34bb6e5  drbd-utils: remove 0001-drbd-8.4.4-drbd-tools-only-rmmod-if-DRBD-is-a-module.patch
     new 864fb16  ceres-solver: add new recipe
     new 60b9eb6  libnih: Add HOMEPAGE info into recipe file.
     new 20eeac7  libtdb: Add HOMEPAGE info into recipe file.
     new 84172c0  mailcap: Add HOMEPAGE info into recipe file.
     new 7454d72  mozjs: Add HOMEPAGE info into recipe file.
     new 47bbfc9  numactl: Add HOMEPAGE info into recipe file.
     new ad97869  orbit2: Add HOMEPAGE info into recipe file.
     new f3469c8  sgpio: Add HOMEPAGE info into recipe file.
     new 50a3814  stunnel: Add HOMEPAGE info into recipe file.

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   (0c2cf2b)
            \
             N -- N -- N   refs/heads/master-next (50a3814)

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 18 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:
 .../libupnp/{libupnp_1.6.21.bb => libupnp1.6_1.6.21.bb}                 | 2 +-
 .../recipes-connectivity/libupnp/{libupnp1.8.bb => libupnp_git.bb}      | 0
 meta-multimedia/recipes-multimedia/gerbera/gerbera_git.bb               | 2 +-
 meta-multimedia/recipes-multimedia/musicpd/mpd_0.19.21.bb               | 2 +-
 4 files changed, 3 insertions(+), 3 deletions(-)
 rename meta-multimedia/recipes-connectivity/libupnp/{libupnp_1.6.21.bb => libupnp1.6_1.6.21.bb} (92%)
 rename meta-multimedia/recipes-connectivity/libupnp/{libupnp1.8.bb => libupnp_git.bb} (100%)

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