[Cmake-commits] CMake branch, nightly, updated. v3.8.0-rc4-705-gc7d6ba9

[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  d93b461ab27cce861df515a422866bf46a36eee6 (commit)
  discards  fbb4fc817f57fd070cc95772359d64a51258f56c (commit)
       via  c7d6ba9119b0fee7716190401c1941b7130f81b6 (commit)
       via  60307c5056476962d7656ea9122ada79a07aa58f (commit)
       via  a9784d0e26a9d9c881248326b2385cefbb732de7 (commit)
       via  b8fc447c1df34eeca1d66acd0e17ca743256d6c2 (commit)
       via  0ae79e4c9548c25fdfb7184c361875ae6f4c214e (commit)
       via  8bb5c14fd8aadc43580625bba0e1be6c93456131 (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 (d93b461ab27cce861df515a422866bf46a36eee6)
            \
             N -- N -- N (c7d6ba9119b0fee7716190401c1941b7130f81b6)

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 +-
 Source/cmGeneratorTarget.cxx |  406 +++++++++++++++---------------------------
 Source/cmGeneratorTarget.h   |   61 ++++---
 3 files changed, 187 insertions(+), 282 deletions(-)


hooks/post-receive
-- 
CMake