For anyone wondering, ignore this. Mistake in the script.
On 05/02/2012 11:28 AM, Richard Heck wrote:
# The branch, 2.0.x, has been updated
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 (f1c4a8fd037019327af9cd99c56ad8da5acd6dbe)
\
N -- N -- N (f79fd6013e8e33a63b23deaaf62c09e9adf7b53b)
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.
