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, neels/cscn has been updated discards 31b17d77f51cc16320855d86a11bfd991e7c4b1e (commit) discards 62bb39483d2bf5de9a694498babd1102a696fc0c (commit) discards 8d53682463c0ca345f5849f965088d24421a7a0c (commit) discards bd2e5ff22aa45c2fa681eb4a282e32a930d4bca3 (commit) discards 54df2e4576fd0b11d31a76e5291a910f7e7fe7f9 (commit) discards fe9950fc7250f56d9be0d6d546da79ac27a714a1 (commit) discards 3aea8193e0f1864c29334720e267bad7e243b5be (commit) via 37b97189019103dc136aa970fab6a8d91a299878 (commit) via 0ad8d6e46cff198664b33dfa75bfb3804aac48bf (commit) via 101db2462b500b49b381f8678f856d74f375b431 (commit) via 19d8f5265921ea79b766233df0eff68d28b874f5 (commit) via a62a6a361791912d3ec75f04261f27094c3235d7 (commit) via bb81326719a30e74e0682932087986b5eb6eedd2 (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 (31b17d77f51cc16320855d86a11bfd991e7c4b1e) \ N -- N -- N (37b97189019103dc136aa970fab6a8d91a299878)
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=37b97189019103dc136aa970fab6a8d91...
commit 37b97189019103dc136aa970fab6a8d91a299878 Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Tue Apr 5 01:17:45 2016 +0200
apply new parameter to osmo_sua_user_create() from libosmo-sccp
http://cgit.osmocom.org/openbsc/commit/?id=0ad8d6e46cff198664b33dfa75bfb3804...
commit 0ad8d6e46cff198664b33dfa75bfb3804aac48bf Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Tue Mar 22 19:25:58 2016 +0100
hack for testing: hardcoded LAC on LU Accept
http://cgit.osmocom.org/openbsc/commit/?id=101db2462b500b49b381f8678f856d74f...
commit 101db2462b500b49b381f8678f856d74f375b431 Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Tue Apr 5 12:04:13 2016 +0200
libiudummy: add dummy iu_tx_paging_cmd()
http://cgit.osmocom.org/openbsc/commit/?id=19d8f5265921ea79b766233df0eff68d2...
commit 19d8f5265921ea79b766233df0eff68d28b874f5 Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Tue Mar 29 18:58:10 2016 +0200
wip: paging
http://cgit.osmocom.org/openbsc/commit/?id=a62a6a361791912d3ec75f04261f27094...
commit a62a6a361791912d3ec75f04261f27094c3235d7 Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Tue Mar 22 19:26:52 2016 +0100
Add registry of RNC-Ids in LACs
Introduce struct gsm_rnc and store in a list. Make it so that the code can be used from both MSC and GPRS.
Add VTY commands 'lac <id>' and 'rnc <id>', which populate above list.
Semantics: when an RNC registers with the MSC or SGSN, it tells us its RNC Id. During paging, we need to find an RNC for a given LAC. The association of RNCs to a particular LAC needs to be configured on the CN side.
http://cgit.osmocom.org/openbsc/commit/?id=bb81326719a30e74e0682932087986b5e...
commit bb81326719a30e74e0682932087986b5eb6eedd2 Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Fri Apr 1 02:17:24 2016 +0200
vty l3 help: fix typo 'comamnds'; fix english s/his//
-----------------------------------------------------------------------
Summary of changes:
hooks/post-receive
osmocom-commitlog@lists.osmocom.org