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 code for Iuh interface".
The branch, sysmocom/iu-cs has been updated discards cc81c6ec16ebfc0555b2a253c82c6c1aa15b6d97 (commit) via 0538cb841c3c18ffd1cce0fbe9697d76cd229b64 (commit) via 7e760acc651da0f0d06dac0b45765b926c6798d1 (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 (cc81c6ec16ebfc0555b2a253c82c6c1aa15b6d97) \ N -- N -- N (0538cb841c3c18ffd1cce0fbe9697d76cd229b64)
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: src/ranap_msg_factory.c | 1 + 1 file changed, 1 insertion(+)
hooks/post-receive