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/mnc3 has been updated
discards d8e49baed8ccaa5c93246fadb9902cf19d90c222 (commit)
via 8fc29594c09b00680d76afbebc40d2c8ef9fea02 (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 (d8e49baed8ccaa5c93246fadb9902cf19d90c222)
\
N -- N -- N (8fc29594c09b00680d76afbebc40d2c8ef9fea02)
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=8fc29594c09b00680d76afbebc40d2c…
commit 8fc29594c09b00680d76afbebc40d2c8ef9fea02
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Wed Feb 21 00:38:05 2018 +0100
implement support for 3-digit MNC with leading zeros
Record the mnc_3_digits flag from SI and pass on via the PCU interface.
Bump the PCU interface version from 7 to 9, since osmo-bsc.git had a pcuif of
version 8 already, and its addition of the mnc_3_digits flag bumped to 9. I am
actually not sure whether this needs to match.
See I78f30aef7aa224b2e9db54c3a844d8f520b3aee0
Depends: Id2240f7f518494c9df6c8bda52c0d5092f90f221 (libosmocore)
Change-Id: I49cd762c3c9d7ee6a82451bdf3ffa2a060767947
-----------------------------------------------------------------------
Summary of changes:
hooks/post-receive
--
Osmocom BTS-side code (Abis, scheduling, ...)