[Cmake-commits] CMake branch, nightly, updated. v3.8.0-rc2-373-g9956b01

[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, nightly has been updated
  discards  a5ba5d4c91e4ee0e783bae0a54c8989f9fb4c7b8 (commit)
  discards  6f1b38f432db822b9eb4f75596a5a06e573b46a1 (commit)
  discards  ca5d0185ca63c2dd2835f5629ac4aea85fbba1d8 (commit)
       via  9956b0118c2b9aba2c38c407bc2fff199a707a6f (commit)
       via  fab6a95a4d0f61a3706ca8fda2ae6b0c01014031 (commit)
       via  79d8942b3df193b5dd95b76092ab6001f449e94d (commit)
       via  01d5963552ca375f04cfdaf21f24aa0d51574a43 (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 (a5ba5d4c91e4ee0e783bae0a54c8989f9fb4c7b8)
            \
             N -- N -- N (9956b0118c2b9aba2c38c407bc2fff199a707a6f)

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:
 Source/CMakeVersion.cmake |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
CMake