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_2G has been updated discards 1d238f7a32f786345fe5db4e1fdce8570033a1d4 (commit) discards 06ddac64b3d419cd73534f5b66bb43a527c3ec1c (commit) discards 0e1c07687d5df947beb5b18adb348029e034d3d1 (commit) discards f12d9e8558a08c01edb53469fcd70104ef81cea6 (commit) via b4c96e0e1ffcae1d91c5ef6e20205a6485b4b97b (commit) via b449eecaa88dc5f93fa707dfe9c894d9642431a5 (commit) via 0ee06dda3f989b90671d8b02add866af80a10de9 (commit) via 2ab3405105b04db82447f89e5079c9e8e2f79a84 (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 (1d238f7a32f786345fe5db4e1fdce8570033a1d4) \ N -- N -- N (b4c96e0e1ffcae1d91c5ef6e20205a6485b4b97b)

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/include/openbsc/vlr.h | 3 ++- openbsc/src/libmsc/gsm_04_08.c | 3 ++- openbsc/src/libvlr/vlr_lu_fsm.c | 19 +++++++++++++------ openbsc/tests/vlr/vlr_test.c | 3 ++- 4 files changed, 19 insertions(+), 9 deletions(-)

hooks/post-receive