[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-631-gc791fb1

[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  eddbd8729d37dd4a4c0ada538868576ff1fe518c (commit)
  discards  45146a43e3b855b41320dcc7b4da1271048c63a3 (commit)
  discards  25e3b0b810e6e0c81890ef55c22ca40100757efd (commit)
  discards  d545708715c4bdc623ca68f2a0f6f848c6e87194 (commit)
       via  c791fb12544926bc5870a61735dc2ec62940a6f6 (commit)
       via  4a553ecb8e52dfd3ca605cd94ef8033e5febe937 (commit)
       via  a466d6f60abe13ddf5eb6bad7cca9743ef67f2f5 (commit)
       via  8772fc81c4ab745eb5abbae58c6a69706f610429 (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 (eddbd8729d37dd4a4c0ada538868576ff1fe518c)
            \
             N -- N -- N (c791fb12544926bc5870a61735dc2ec62940a6f6)

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