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 BTS-side code (Abis, scheduling, ...)".

The branch, master has been updated discards 2c541c652d1524c9770849c65cef9b3d039008bf (commit) via cb20c83323da485ff392ccffa7ec75de8e2ffede (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 (2c541c652d1524c9770849c65cef9b3d039008bf) \ N -- N -- N (cb20c83323da485ff392ccffa7ec75de8e2ffede)

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/osmo-bts/commit/?id=cb20c83323da485ff392ccffa7ec75de...

commit cb20c83323da485ff392ccffa7ec75de8e2ffede Author: Max msuraev@sysmocom.de Date: Thu Feb 18 17:48:07 2016 +0100

Fix ocmo-bts-octphy interaction with OsmoPCU

Previously osmo-bts-octphy have not provided in-band presence information which cause off-by-one errors and misinterpretation of ph_data_ind by PCU. This fixed now by adding support for explicitly passing PH-DATA presence info. Corresponding check and in-band passing of presence information are removed.

Note: this requires libosmocore version with osmo_ph_pres_info_type support integrated.

[hfreyther/max: Remove + 1 from the decoded length]

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

Summary of changes:

hooks/post-receive