This is an automated email from the ASF dual-hosted git repository.
khmarbaise pushed a change to branch MSHARED-747
in repository https://gitbox.apache.org/repos/asf/maven-archiver.git.
discard 9b69c6d fixup! fixup! fixup! [MSHARED-747] - Upgrade maven-plugins
parent to version 32
discard 535e234 fixup! fixup! [MSHARED-747] - Upgrade maven-plugins parent to
version 32
discard e50bfb1 fixup! [MSHARED-747] - Upgrade maven-plugins parent to
version 32
discard 504106e [MSHARED-747] - Upgrade maven-plugins parent to version 32
add 9111b94 Fixed Unit test.
new 8e78c1c [MSHARED-747] - Upgrade maven-plugins parent to version 32
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 (9b69c6d)
\
N -- N -- N refs/heads/MSHARED-747 (8e78c1c)
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 1 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:
