This is an automated email from the ASF dual-hosted git repository.
michaelo pushed a change to branch MSHARED-1032
in repository https://gitbox.apache.org/repos/asf/maven-site-plugin.git
omit 3691530c [MSITE-970] Upgrade to Maven Reporting API 4.0.0-M7, Maven
Reporting Impl 4.0.0-M9, Maven Reporting Exec 2.0.0-M9
omit 057107f2 [MSITE-969] Upgrade to Doxia 2.0.0-M7/Doxia Sitetools
2.0.0-M11
add 3e421339 [MSITE-965] Add system requirements history
add 8aa54120 [MSITE-969] Upgrade to Doxia 2.0.0-M7/Doxia Sitetools
2.0.0-M11
add 0e4b54e8 [MSITE-970] Upgrade to Maven Reporting API 4.0.0-M7, Maven
Reporting Impl 4.0.0-M9, Maven Reporting Exec 2.0.0-M9
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 (3691530c)
\
N -- N -- N refs/heads/MSHARED-1032 (0e4b54e8)
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:
pom.xml | 35 +++++++++++++++++++++++++++++++++++
src/site/apt/history.apt | 26 ++++++++++++++++++++++----
2 files changed, 57 insertions(+), 4 deletions(-)
