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 "OpenBTS' transceiver retro-fit". The branch, fairwaves/pending has been updated discards ffba9779246fc9ac7ca3e001f85d6ce1a25e0192 (commit) discards c777a761c570c9f2b5ff17a39134014006fc96f0 (commit) via 6512812e43179ae3e4bf85c3203f11e281f19cd0 (commit) via ded68da44f1b9641e920231be596a4ca8add198b (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 (ffba9779246fc9ac7ca3e001f85d6ce1a25e0192) \ N -- N -- N (6512812e43179ae3e4bf85c3203f11e281f19cd0) 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-trx/commit/?id=6512812e43179ae3e4bf85c3203f11e… commit 6512812e43179ae3e4bf85c3203f11e281f19cd0 Author: Alexander Chemeris <Alexander.Chemeris(a)gmail.com> Date: Thu Jun 4 19:05:28 2015 -0400 sigProcLib: Check for bogus TOA before using it. http://cgit.osmocom.org/osmo-trx/commit/?id=ded68da44f1b9641e920231be596a4c… commit ded68da44f1b9641e920231be596a4ca8add198b Author: Alexander Chemeris <Alexander.Chemeris(a)gmail.com> Date: Thu Jun 4 15:39:41 2015 -0400 Transceiver: Fix clipping detection. There are two primary changes in this commit: 1) Return values of detect functions changed form bool to int to actually pass the return value from the inner function and notify higher levels about clipping. Previously the information was lost due to conversion to bool. 2) Clipping level is not the final verdict now. We still try to demod a burst and mark it as clipped only if the level is above the clipping level AND we can't demod it. The reasoning for this is that in real life we want to do as much as possible to demod the burst, because we want to get as much from our dynamic range as possible. So a little bit of clipping is fine and is expected. We just don't want too much of it to break our demod. ----------------------------------------------------------------------- Summary of changes: hooks/post-receive -- OpenBTS' transceiver retro-fit