[Cmake-commits] CMake branch, next, updated. v3.8.0-769-gbe2c45f

[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  81ad2d8a967d4b812520daea37b8c6e7da062493 (commit)
  discards  ce09f773f7fafd604b9f1973b0871091d80fd1c5 (commit)
  discards  7e57e70127d308457cf2824701d9d283b2ca1e4d (commit)
  discards  0d4c2fe4930a8e445bf6425769655f6073fa8aa9 (commit)
  discards  8eae3a742060f36d66310ebd4365b13d0759816e (commit)
       via  be2c45f2a98d69cc9952b592777bb506f69149a2 (commit)
       via  c003f1b996fdc6ff9e2542c21578d5cf04153247 (commit)
       via  ddd2b02455db9b0ef3604af1b9b10c22af56bff9 (commit)
       via  d4db7a2ec0c4f1ebbfc98984672793f5d9eb2744 (commit)
       via  c0323cbf5f407e9a231c8e7d55801ef3723748bd (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 (81ad2d8a967d4b812520daea37b8c6e7da062493)
            \
             N -- N -- N (be2c45f2a98d69cc9952b592777bb506f69149a2)

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