This is an automated email from the ASF dual-hosted git repository.

khmarbaise pushed a change to branch MSHARED-695
in repository https://gitbox.apache.org/repos/asf/maven-deploy-plugin.git.


 discard 99cc768  Using special version from branch.
 discard 85e380e  [MSHARED-695] - WIP - Move checksum generation from install 
to deploy
     add a2e826f  [MDEPLOY-235] - Upgrade mave-surefire/failsafe-plugin 2.21.0
     add d7e07cb  [MNGSITE-332] - Changed download templates of plugins not to 
reference .md5 anymore
     new fac5dbd  [MSHARED-695] - WIP - Move checksum generation from install 
to deploy
     new ff58ff0  Using special version from branch.

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   (99cc768)
            \
             N -- N -- N   refs/heads/MSHARED-695 (ff58ff0)

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:
 pom.xml                       | 1 +
 src/site/xdoc/download.xml.vm | 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)

-- 
To stop receiving notification emails like this one, please contact
khmarba...@apache.org.

Reply via email to