This is an automated email from the ASF dual-hosted git repository.
elharo pushed a change to branch elharo-patch-7
in repository https://gitbox.apache.org/repos/asf/maven-site.git.
discard 903a06e Merge branch 'elharo-patch-7' of github.com:apache/maven-site
into elharo-patch-7
discard 5a72d08 [MNGSITE-415] say Maven 3.0.x is EOL
discard 73bc27a Merge branch 'elharo-patch-7' of github.com:apache/maven-site
into elharo-patch-7
discard bad6be8 update id
discard 251aa9c [MNGSITE-415] say Maven 3.0.x is EOL
discard fb0a8e0 Merge branch 'master' into elharo-patch-7
discard 1ea893e update id
discard 373abd6 [MNGSITE-415] say Maven 3.0.x is EOL
add 3940e07 [MNGSITE-415] say Maven 3.0.x is EOL
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (903a06e)
\
N -- N -- N refs/heads/elharo-patch-7 (3940e07)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
