13 Jul
2016
13 Jul
'16
5:50 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 "The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)".
The branch, osmocom/jenkins-test has been updated
discards 1083c9119d42f56fe4590a39532e43239e6511b6 (commit)
discards 3a2c2bb781fc6cf44ba3e0da3475a7a7a503012d (commit)
via 9759374adbb632ff5f8a4b739e0f62a9c9017622 (commit)
via a3d93ed2f9c114634b749c1304039e709a21a270 (commit)
via 575420637981828b64c1292ada015d7170b89390 (commit)
via 176b62a80c0170f1b9a1578d0b16c3ef27cf1a8f (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 (1083c9119d42f56fe4590a39532e43239e6511b6)
\
N -- N -- N (9759374adbb632ff5f8a4b739e0f62a9c9017622)
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/openbsc/commit/?id=9759374adbb632ff5f8a4b739e0f62a9…
commit 9759374adbb632ff5f8a4b739e0f62a9c9017622
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Mon Jul 11 19:44:58 2016 +0200
jenkins.sh: add --enable-iu matrix build
Change-Id: Ida76f24d0b801fa609f3a128b3b912572cad4297
http://cgit.osmocom.org/openbsc/commit/?id=a3d93ed2f9c114634b749c1304039e70…
commit a3d93ed2f9c114634b749c1304039e709a21a270
Author: Neels Hofmeyr <neels(a)hofmeyr.de>
Date: Mon Jul 11 19:39:51 2016 +0200
jenkins.sh: remove code dup
Have a bash function to build each dependency with the same commands. There is
a tradeoff: having each dependency build with the same function means you can't
easily tweak one of the dependencies. OTOH having a unified function means a)
more readable script, b) that we're sure not to forget some steps and c) no
need to do the same edit n times.
Set the PKG_CONFIG_PATH globally. Also a tradeoff: if a future addition
wouldn't need the same PKG_CONFIG_PATH, this would make things ugly. But that
is actually quite unlikely, and the readability improvement is substantial.
Use env variables to remember local paths. That means we always are sure to cd
to the same absolute base path, which a 'cd ..' can't guarantee; also, we
avoid
possible typos for e.g. "$deps/install".
Change-Id: Ib23f86c6cc1441d882de59bcdde5de87fa4e9fdf
-----------------------------------------------------------------------
Summary of changes:
debian/changelog | 2 ++
openbsc/include/openbsc/osmux.h | 1 +
openbsc/src/gprs/sgsn_vty.c | 17 ++++++++++++++---
openbsc/src/libmgcp/mgcp_protocol.c | 6 +++---
openbsc/src/osmo-bsc_nat/bsc_mgcp_utils.c | 5 +++--
openbsc/tests/vty_test_runner.py | 2 ++
6 files changed, 25 insertions(+), 8 deletions(-)
hooks/post-receive
--
The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)