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, vlr_3G has been updated discards b1eb2c9762174c0238b2d826c713ac89c1136f71 (commit) discards 9235fe07eb0b622a0bc130d8470a4690d6a3517f (commit) discards a0a574be34816231eb1bcdade33d1f70c807e0de (commit) discards 579051f5c210758e1d90d118da52218beba490da (commit) discards 31159746274c27183a0020df886fbac71601af3c (commit) via e1148dfa6c2dcfaeaae3fc068d3de645f0e34182 (commit) via f8d8c91a69b45b6451aff9e68f091a6357aad710 (commit) via d4000accf9bd7097cd188150706fe70d78e7cb58 (commit) via a7cfcabd3b8276e86796d5f3c1236c9a14e8e34c (commit) via ebff45e2ee89bd8c3cb106a58da3b172c01467e1 (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 (b1eb2c9762174c0238b2d826c713ac89c1136f71) \ N -- N -- N (e1148dfa6c2dcfaeaae3fc068d3de645f0e34182) 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 ----------------------------------------------------------------- ----------------------------------------------------------------------- Summary of changes: openbsc/src/libbsc/abis_rsl.c | 2 -- 1 file changed, 2 deletions(-) hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)