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 "Osmocom BTS-side code (Abis, scheduling, ...)". The branch, fairwaves/package has been updated discards b7a6427a89e6a2f726a2b96c9897926e4cdb032d (commit) discards 949fcade616f25ceb98c187feaee9040b2f3e46b (commit) discards a53e3a547299b202235afad9801acacd5cfe4acd (commit) via bfa59a46cb0786e09d48acb245bde39a9092363d (commit) via 64d16028eb7d38bb442591c6c0224ae28eb3e2be (commit) via 70c68853c289bf13822a7c76cd2434fcf7364576 (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 (b7a6427a89e6a2f726a2b96c9897926e4cdb032d) \ N -- N -- N (bfa59a46cb0786e09d48acb245bde39a9092363d) 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/osmo-bts/commit/?id=bfa59a46cb0786e09d48acb245bde39a... commit bfa59a46cb0786e09d48acb245bde39a9092363d Author: Ivan Kluchnikov <kluchnikovi@gmail.com> Date: Thu Feb 16 22:24:27 2017 +0300 debian: Update changelog to 0.5.0-fw.1 Change-Id: Ibd62d183cd1f6c33d6d942398a821abf3d3d70ee ----------------------------------------------------------------------- Summary of changes: src/common/oml.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)