[Cmake-commits] CMake branch, nightly, updated. v3.8.0-rc2-504-gb7d2d37

[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  5f196337f169ebb86d98ed233e8ed75efad1dc16 (commit)
  discards  f1568956177b4043f1412396afd7ee35cb6ef5a2 (commit)
  discards  2e17ce4c97c46970a3e53761890fad25370a7189 (commit)
  discards  1374b49914e4dafbf40692db0fa611c82cdba71d (commit)
       via  b7d2d374017f940a7f66611d027ff2175c2c91a5 (commit)
       via  6a839be65977e295f58030b58b6f942473400f56 (commit)
       via  ec8e62fd7e8b10860a57d2526cbc8039e171c8e0 (commit)
       via  038bd5e0b5e389c4325f3a0feec9dcc7a0c58c9c (commit)
       via  baba0a435a9f715c3f3e399b8284f25e558a5bad (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 (5f196337f169ebb86d98ed233e8ed75efad1dc16)
            \
             N -- N -- N (b7d2d374017f940a7f66611d027ff2175c2c91a5)

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