The branch, twofactorauth has been updated discards 506400a2911c3e7b6f9bf9611c9f1a0a8eabe3f5 (commit) via 79aee8f21c4519a76b3eb47b9fdc9230734cd03d (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 (506400a2911c3e7b6f9bf9611c9f1a0a8eabe3f5) \ N -- N -- N (79aee8f21c4519a76b3eb47b9fdc9230734cd03d) 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: The diff of changes is: hooks/post-receive -- python-x2go.git (Python X2Go Client API) 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 "python-x2go.git" (Python X2Go Client API).