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 "UNNAMED PROJECT". The branch, jerlbeck/master has been updated discards 377250f3ada5701a104ccb5388bfe13640b53eb7 (commit) via c91c18e6ef9ee5fca3d10b57ebddf211d3655a8d (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 (377250f3ada5701a104ccb5388bfe13640b53eb7) \ N -- N -- N (c91c18e6ef9ee5fca3d10b57ebddf211d3655a8d) 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 -- UNNAMED PROJECT