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, next has been updated
discards e73c111a7d4a229da1bff81ba3f58509112392a8 (commit)
discards b4e8cb1ee309cd11df97c8f56884f889c1bdeaab (commit)
discards f18741aebb0a5f15927e5f8f449d4e4d53f4ef47 (commit)
discards 7c14ff1217bdc368b988bdd6d8ee4280349c175b (commit)
via 09f85c98c0f52a8f58cde0ffc3949316e4c874a2 (commit)
via 01bdc2cc43def6797e40037859cb72981c7342b8 (commit)
via e145cfe2e9d4afac060754097dee0b9439d470d7 (commit)
via f89678f60948241355959fedc2d6239db1bedcd6 (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 (e73c111a7d4a229da1bff81ba3f58509112392a8)
\
N -- N -- N (09f85c98c0f52a8f58cde0ffc3949316e4c874a2)
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:
Help/release/dev/{Autogen_source_group => Autogen_source_group.rst} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename Help/release/dev/{Autogen_source_group => Autogen_source_group.rst}
(100%)
hooks/post-receive
--
CMake
_______________________________________________
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits
