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 "SCCP Library".
The branch, sysmocom/iu has been updated
discards 4971134acada31aa1c788aaa095b6a2b8c3c4860 (commit)
discards 1a4e3791123b6194feb7163630f56151eba60d42 (commit)
discards 57bad484ab88f6f26f5287c32beea86c9e353a01 (commit)
via 545909d54a0ab0e5f65dad3d536605453e6c62f6 (commit)
via bf71df1001fedc90431a17942127e9bca31f4a3c (commit)
via 412b8177b558f9ea553a4a62e976abd7280a7d52 (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 (4971134acada31aa1c788aaa095b6a2b8c3c4860)
\
N -- N -- N (545909d54a0ab0e5f65dad3d536605453e6c62f6)
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:
hooks/post-receive
--
SCCP Library
Show replies by date