This is an automated email from the ASF dual-hosted git repository.
michaelo pushed a change to branch doxia-2.0.0
in repository https://gitbox.apache.org/repos/asf/maven-javadoc-plugin.git
discard a40b7038 Align plugin with AbstractMavenReport
discard 1952d598 Prepare for Doxia 2.0.0
add e6e6180e Remove junk from 692d7a8a9918efd24633a44f0f3d4dfd22d0fec4
new 9733542b Prepare for Doxia 2.0.0
new 1ed58816 Align plugin with AbstractMavenReport
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 (a40b7038)
\
N -- N -- N refs/heads/doxia-2.0.0 (1ed58816)
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.
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
null-null.jar | Bin 92898 -> 0 bytes
1 file changed, 0 insertions(+), 0 deletions(-)
delete mode 100644 null-null.jar
