2 Jun
2017
2 Jun
'17
10:39 p.m.
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, neels/test has been updated
discards eb218f78b85698f8be12914112a5de30b3812694 (commit)
discards b1fdbc952f807cfe341e67819f520b3e16e2bb15 (commit)
via 51c2e69b62a9b7c428318bb635a049e4041369b6 (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 (eb218f78b85698f8be12914112a5de30b3812694)
\
N -- N -- N (51c2e69b62a9b7c428318bb635a049e4041369b6)
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=51c2e69b62a9b7c428318bb635a049e…
commit 51c2e69b62a9b7c428318bb635a049e4041369b6
Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de>
Date: Fri Jun 2 19:38:07 2017 +0200
Revert "Add version to phy_instance"
This reverts commit 9eeb0b1a136fc8c24a86cb4d832c264674c10db0.
After this commit, osmo-gsm-tester test runs for the sysmoBTS failed with
SIGABRT consistently. See below issue:
Change-Id: I2c9fd5e6739c1750365c0241476ce4b1aa2df3d4
Related: OS#2316
-----------------------------------------------------------------------
Summary of changes:
src/common/oml.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
Osmocom BTS-side code (Abis, scheduling, ...)