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 "CMake".
The branch, next has been updated
discards ce9c4b4d2867c9704fb75020b4f310c6db25a431 (commit)
via c26885066b2a7a76e5ae97f2bfc7282f8182bed8 (commit)
via cb0f3cbb8e2e34e1948598355e151aee4953f7f6 (commit)
via 18eeed41948b265168497ea3360e7b0d56e8e8a9 (commit)
via cb4e731347e255f2bbb1f2d9593d8080c8718c5b (commit)
via 6ca509e7c65a94f4b486bacef766bac717f5308f (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 (ce9c4b4d2867c9704fb75020b4f310c6db25a431)
\
N -- N -- N (c26885066b2a7a76e5ae97f2bfc7282f8182bed8)
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
--
CMake
_______________________________________________
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits
