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 cca0fbc067eb2bdfb74dd87a714562db5f236940 (commit)
discards 8a6a1f4984644e1eb20d9bdc866e9ae8c1c7e375 (commit)
discards 9be47180bdc5d7a885bfd9c311f8651ca5c64eb5 (commit)
discards 68af5c53530ab356f86237c6d12928f36e1396c9 (commit)
via 5f196337f169ebb86d98ed233e8ed75efad1dc16 (commit)
via f1568956177b4043f1412396afd7ee35cb6ef5a2 (commit)
via 2e17ce4c97c46970a3e53761890fad25370a7189 (commit)
via 1374b49914e4dafbf40692db0fa611c82cdba71d (commit)
via 14f0378e103fd24915712cb94c98265ad18c8736 (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 (cca0fbc067eb2bdfb74dd87a714562db5f236940)
\
N -- N -- N (5f196337f169ebb86d98ed233e8ed75efad1dc16)
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
_______________________________________________
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits
