[Cmake-commits] CMake branch, nightly, updated. v3.8.0-rc2-372-ga5ba5d4

[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  e6cd443763d90583d1664403619979b4bce44393 (commit)
  discards  fddee0f94de26cd9540becfca7ad81716023f767 (commit)
  discards  de21e3afaad243f15577d8bc1b20a76c563680d7 (commit)
       via  a5ba5d4c91e4ee0e783bae0a54c8989f9fb4c7b8 (commit)
       via  6f1b38f432db822b9eb4f75596a5a06e573b46a1 (commit)
       via  ca5d0185ca63c2dd2835f5629ac4aea85fbba1d8 (commit)
       via  d96d971ac048acc8fa266b2e1320cc7f0470aeae (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 (e6cd443763d90583d1664403619979b4bce44393)
            \
             N -- N -- N (a5ba5d4c91e4ee0e783bae0a54c8989f9fb4c7b8)

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