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 "An utility library for Open Source Mobile Communications". The branch, laforge/pending has been updated discards f82de6f6b7bc94084eb517a03cb35bc23e8811da (commit) discards 9eb59be6e7495a38309cbfabdd654a155a18f17a (commit) via 88254890c4aaa7c3771fc9b387554392679b23aa (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 (f82de6f6b7bc94084eb517a03cb35bc23e8811da) \ N -- N -- N (88254890c4aaa7c3771fc9b387554392679b23aa) 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/libosmocore/commit/?id=88254890c4aaa7c3771fc9b387554... commit 88254890c4aaa7c3771fc9b387554392679b23aa Author: Harald Welte <laforge@gnumonks.org> Date: Wed Apr 20 17:28:03 2016 +0200 add new header file for TS 23.003 ----------------------------------------------------------------------- Summary of changes: hooks/post-receive -- An utility library for Open Source Mobile Communications