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 9a2c6655686fb773550b6e1050f60c821eee70b4 (commit)
via 3db617f14a0314a0e2a233b3ddaba1501213c0e5 (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 (9a2c6655686fb773550b6e1050f60c821eee70b4)
\
N -- N -- N (3db617f14a0314a0e2a233b3ddaba1501213c0e5)
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
Show replies by date