This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-commitlog@lists.osmocom.org/.
gitosis at osmocom.org gitosis at osmocom.orgThis 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, vlr_3G has been updated discards ed868ec1e68de7a359ae5c1bd8147e2524f0bb11 (commit) discards 33f428ed51165a2e3da2d6ed95ddd2ae47787a30 (commit) discards ef86d12d62695148154b6099812867464806a66c (commit) discards b42b32736912acf7a178dec6a00efebdbd6feaad (commit) via 2e8ecf3af3c1ffab29357f45e4576b2d3b9268e4 (commit) via 581ffc9d7bee9b6ea238fc2014007aab4cbe5315 (commit) via 0aae05474790bf1d3b4d7ce369611892873443b5 (commit) via a2697738cc08e2e6528c09bb7775f1793cff37b8 (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 (ed868ec1e68de7a359ae5c1bd8147e2524f0bb11) \ N -- N -- N (2e8ecf3af3c1ffab29357f45e4576b2d3b9268e4) 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=2e8ecf3af3c1ffab29357f45e4576b2d3b9268e4 commit 2e8ecf3af3c1ffab29357f45e4576b2d3b9268e4 Author: Neels Hofmeyr <nhofmeyr at sysmocom.de> Date: Mon May 30 15:09:47 2016 +0200 temporary dev: set debug log level almost everywhere Change-Id: I0d5a36560e7edde27497de57e579f5b1d00eb525 http://cgit.osmocom.org/openbsc/commit/?id=581ffc9d7bee9b6ea238fc2014007aab4cbe5315 commit 581ffc9d7bee9b6ea238fc2014007aab4cbe5315 Author: Neels Hofmeyr <nhofmeyr at sysmocom.de> Date: Fri Mar 10 02:15:20 2017 +0100 log protocol discriminators and message types by name Depends: libosmocore change-id I0fca8e95ed5c2148b1a7440eff3fc9c7583898df Change-Id: If1c49faf6e1757cb16b383dd2db87b48bc94eee6 http://cgit.osmocom.org/openbsc/commit/?id=0aae05474790bf1d3b4d7ce369611892873443b5 commit 0aae05474790bf1d3b4d7ce369611892873443b5 Author: Neels Hofmeyr <nhofmeyr at sysmocom.de> Date: Thu Mar 16 16:14:34 2017 +0100 mgcp: hack RAB success from nano3G: patch first RTP payload The ip.access nano3G needs the first RTP payload's first two bytes to read hex 'e400', or it will reject the RAB assignment. Add flag patched_first_rtp_payload to mgcp_rtp_state to detect the first RTP payload on a stream, and overwrite its first bytes with e400. This should probably be configurable, but seems to not harm other femto cells (as long as we patch only the first RTP payload in each stream). Only do this when sending to the BTS side. Change-Id: I31a4475f42d59fd5704d52ee6e473e270db6d779 http://cgit.osmocom.org/openbsc/commit/?id=a2697738cc08e2e6528c09bb7775f1793cff37b8 commit a2697738cc08e2e6528c09bb7775f1793cff37b8 Author: Neels Hofmeyr <nhofmeyr at sysmocom.de> Date: Fri May 20 21:59:55 2016 +0200 Implement IuCS (large refactoring and addition) osmo-nitb becomes osmo-msc add DIUCS debug log constant add iucs.[hc] add msc vty, remove nitb vty add libiudummy, to avoid linking Iu deps in tests Use new msc_tx_dtap() instead of gsm0808_submit_dtap() libmgcp: add mgcpgw client API bridge calls via mgcpgw mgcp: hack RAB success from nano3G: patch first RTP payload The ip.access nano3G needs the first RTP payload's first two bytes to read hex 'e400', or it will reject the RAB assignment. Add flag patched_first_rtp_payload to mgcp_rtp_state to detect the first RTP payload on a stream, and overwrite its first bytes with e400. This should probably be configurable, but seems to not harm other femto cells (as long as we patch only the first RTP payload in each stream). Only do this when sending to the BTS side. Change-Id: Ie13ff348117e892d41b8355ab6c24915301eaeaf ----------------------------------------------------------------------- Summary of changes: openbsc/doc/examples/osmo-bsc_mgcp/mgcp.cfg | 8 +- openbsc/doc/examples/osmo-msc/osmo-msc.cfg | 1 + .../osmo-nitb/bs11/openbsc-1bts-2trx-hopping.cfg | 164 --------------- .../examples/osmo-nitb/bs11/openbsc-1bts-2trx.cfg | 84 -------- .../examples/osmo-nitb/bs11/openbsc-2bts-2trx.cfg | 148 -------------- openbsc/doc/examples/osmo-nitb/bs11/openbsc.cfg | 56 ------ .../osmo-nitb/nanobts/openbsc-multitrx.cfg | 99 ---------- openbsc/doc/examples/osmo-nitb/nanobts/openbsc.cfg | 77 -------- .../osmo-nitb/nokia/openbsc_nokia_3trx.cfg | 117 ----------- openbsc/doc/examples/osmo-nitb/rbs2308/openbsc.cfg | 220 --------------------- .../doc/examples/osmo-nitb/sysmobts/openbsc.cfg | 77 -------- 11 files changed, 5 insertions(+), 1046 deletions(-) delete mode 100644 openbsc/doc/examples/osmo-nitb/bs11/openbsc-1bts-2trx-hopping.cfg delete mode 100644 openbsc/doc/examples/osmo-nitb/bs11/openbsc-1bts-2trx.cfg delete mode 100644 openbsc/doc/examples/osmo-nitb/bs11/openbsc-2bts-2trx.cfg delete mode 100644 openbsc/doc/examples/osmo-nitb/bs11/openbsc.cfg delete mode 100644 openbsc/doc/examples/osmo-nitb/nanobts/openbsc-multitrx.cfg delete mode 100644 openbsc/doc/examples/osmo-nitb/nanobts/openbsc.cfg delete mode 100644 openbsc/doc/examples/osmo-nitb/nokia/openbsc_nokia_3trx.cfg delete mode 100644 openbsc/doc/examples/osmo-nitb/rbs2308/openbsc.cfg delete mode 100644 openbsc/doc/examples/osmo-nitb/sysmobts/openbsc.cfg hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)