[Cmake-commits] CMake branch, next, updated. v3.8.0-rc2-615-g8047bd6

[Kitware Robot]

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  13908eae4145346aff2b324e048d6235b06a02c1 (commit)
  discards  4f9021ac1502039025ec4a10cf3e09b80fffd5ac (commit)
  discards  3e912713838afff53f8375836adf9a71779a8d34 (commit)
       via  8047bd6c0d935d8c0cc303b26d75ee62973d2b7f (commit)
       via  5bded841b4d66bea70c932184eac0a44b82d03fe (commit)
       via  0f4420e0a80993ccd6ce7d51eeb96e904b8bd9f8 (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 (13908eae4145346aff2b324e048d6235b06a02c1)
            \
             N -- N -- N (8047bd6c0d935d8c0cc303b26d75ee62973d2b7f)

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