This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Osmocom layer for OpenEmbedded".

The branch, laforge/nightly has been updated discards 8172c8ed924e2e6e4c5e417d857b602e53038105 (commit) discards e89c42dc4261edcfacf7f12c498fdb285a5063ab (commit) discards 1dfd9cdad0798f478a4482bc2ab106a05648b4e8 (commit) discards c93542b049089466e013c941dc3f1ad2f3b756ca (commit) discards c0208ebe70115a0ae6597ea7397a01c4de77576c (commit) discards 26dcbe02691cf4bfea7dc2d3c7e77b2633d3526a (commit) discards 848f7f56a2eed842faa5d173dcbf1991bf2d16a3 (commit) discards 1c92a0cf1ef922016c1b8c178f4d3a7554af8902 (commit) via ea485e006d059f28e7fb7649d156e3677406ff59 (commit) via fdbb433446fc698370124fb9444fcbde31c84285 (commit) via 266820ad9e25d1a3bb27730e0ea070b7dc782766 (commit) via cb1bb2b0628ace82944f47e7e87563b63449a6ce (commit) via b4531911489c0a49e8e04b9107dc639d2b753288 (commit) via 3ad2ad5dc455b3e773f257808a2c8f5d74f59162 (commit) via 0979bed839b716e8a574517ed2a987f9117d0287 (commit) via a3d306e76095302944afc95131208924e0d3d424 (commit) via 146edc71f57820db204e80dd9bc508e2643c5f0a (commit)

This update added new revisions after undoing existing revisions. That is to say, the old revision is not a strict subset of the new revision. This situation occurs when you --force push a change and generate a repository containing something like this:

* -- * -- B -- O -- O -- O (8172c8ed924e2e6e4c5e417d857b602e53038105) \ N -- N -- N (ea485e006d059f28e7fb7649d156e3677406ff59)

When this happens we assume that you've already had alert emails for all of the O revisions, and so we here report only the revisions in the N branch from the common base, B.

Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below.

- Log ----------------------------------------------------------------- http://cgit.osmocom.org/meta-telephony/commit/?id=ea485e006d059f28e7fb7649d1...

commit ea485e006d059f28e7fb7649d156e3677406ff59 Author: Harald Welte laforge@gnumonks.org Date: Thu Jun 23 08:51:51 2016 +0200

set up osmocom recipes with AUTOREV to track git master

This is for the upcoming nightly builds, where all our osmo* recipes are going to track current master of their respective upstream git repository.

Change-Id: Idda98bdfa07c16aee1955fa63373b358bb754c90

-----------------------------------------------------------------------

Summary of changes:

hooks/post-receive