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/patches-pending has been updated discards 92d80aa186b59bcef96a9c623a6e61d2bcf7d673 (commit) discards 4b5ac247c18f612db6225ff53e23cee3fae233d8 (commit) discards e305755b61d946c5be8d7fa0a4d50df6a17a6fc8 (commit) discards 91d4f5f08110c467a6e94f4464a46e56629061e7 (commit) via a8d33d4bdf76a4ef465f2710400b43a7bbd5d664 (commit) via 31b1f19b5b975bf2a9ed034120625aa70cff77d5 (commit) via a044481568b675cdb1ae1b9de1dad0e5a21565b2 (commit) via 6a2fa9290f7aa8a21c2c5383d532a361a23c53e5 (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 (92d80aa186b59bcef96a9c623a6e61d2bcf7d673) \ N -- N -- N (a8d33d4bdf76a4ef465f2710400b43a7bbd5d664) 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=a8d33d4bdf76a4ef465f2710400b43a7… commit a8d33d4bdf76a4ef465f2710400b43a7bbd5d664 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Mon Mar 14 13:41:20 2016 +0100 bsc_scan_msc_msg: check protocol discriminator The function assumed an MM protocol discriminator without verifying it. http://cgit.osmocom.org/openbsc/commit/?id=31b1f19b5b975bf2a9ed034120625aa7… commit 31b1f19b5b975bf2a9ed034120625aa70cff77d5 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Mon Mar 7 16:48:38 2016 +0100 fix confusing typo in constant (THAN -> THEN) http://cgit.osmocom.org/openbsc/commit/?id=a044481568b675cdb1ae1b9de1dad0e5… commit a044481568b675cdb1ae1b9de1dad0e5a21565b2 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Mon Mar 14 14:36:56 2016 +0100 04.08: apply new transaction id inline functions libosmocore recently added inline functions to relieve callers from applying bitmasks and bit shifts to access the transaction id of a GSM 04.08 header. Apply these functions. http://cgit.osmocom.org/openbsc/commit/?id=6a2fa9290f7aa8a21c2c5383d532a361… commit 6a2fa9290f7aa8a21c2c5383d532a361a23c53e5 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Thu Mar 10 12:19:13 2016 +0100 04.08: apply new bitmask functions, fix bitmask use Replace hardcoded protocol discriminator and message type bitmasks with function calls recently introduced in libosmocore. Note that the release 98 bitmasks slightly differ from the release 99 bitmasks. This patch uses the "default" gsm48_hdr_msg_type invocation, thus it depends on libosmocore whether 98 or 99 bitmasks are used. In some places, use of the bitmask was erratic. Fix these implicitly by employing the bitmask functions: * silent_call.c: silent_call_reroute(): add missing bitmask for MM. * bsc_msg_filter.c: bsc_msg_filter_initial(): RR vs. MM messages. * osmo_bsc_filter.c: bsc_find_msc() and bsc_scan_bts_msg(): RR vs. MM messages. * bsc_nat_rewrite.c: bsc_nat_rewrite_msg(): SMS vs. CC messages. * bsc_ussd.c: no bitmask is applicable for the message types used here. * gb_proxy.c: gbproxy_imsi_acquisition(): missing bit mask for pdisc. In gprs_gb_parse.c: gprs_gb_parse_dtap(), add a log notice for unexpected message types. ----------------------------------------------------------------------- Summary of changes: hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)