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/embedded has been updated discards 52aca0510a5f9f19f086dd3d8011d0819229bed9 (commit) via 1859277a74eb69693e3518761d844caac2172e11 (commit) via ba3befe7e5299ca3e6895201b4557b855bc4f561 (commit) via ac9e2d8aa52cbc4198cd94ab9d9c92c3317a979f (commit) via 35b54d12bbedd61562bd9f5a3131024a166a4835 (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 (52aca0510a5f9f19f086dd3d8011d0819229bed9) \ N -- N -- N (1859277a74eb69693e3518761d844caac2172e11) 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: include/osmocom/gsm/tlv.h | 4 ++-- src/timer.c | 3 +-- tests/fsm/fsm_test.c | 4 +++- 3 files changed, 6 insertions(+), 5 deletions(-) hooks/post-receive -- An utility library for Open Source Mobile Communications