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-artifact-transfer.git.


 discard 2287160  Added debug output.
 discard f748d83  [MSHARED-695] - WIP - Move checksum generation from install 
to deploy  o Moved checksum generation into deploy part. Removed checksum from  
  install.  o Removed it from ProjectInstallerRequest.
 discard f949b2e  [MSHARED-695] - WIP - Move checksum generation from install 
to deploy  o Moved checksum generation into deploy part. Removed checksume from 
   install
 discard 66a6b3c  [MSHARED-695] - WIP - Move checksum generation from install 
to deploy
 discard 5f21cc0  [MSHARED-695] - WIP - Move checksum generation from install 
to deploy
 discard 996cd85  [MSHARED-695] - WIP - Move checksum generation from install 
to deploy
 discard a0e1f30  [MSHARED-695] - WIP - Move checksum generation from install 
to deploy
 discard bfc522e  Add JDK10 and test it.
     add b900eea  [MSHARED-724] - Upgrade mave-surefire/failsafe-plugin 2.21.0
     new 46ee12f  Add JDK10 and test it.
     new 46de489  [MSHARED-695] - WIP - Move checksum generation from install 
to deploy
     new f934aeb  [MSHARED-695] - WIP - Move checksum generation from install 
to deploy
     new b539253  [MSHARED-695] - WIP - Move checksum generation from install 
to deploy
     new e3de664  [MSHARED-695] - WIP - Move checksum generation from install 
to deploy
     new 894fa27  [MSHARED-695] - WIP - Move checksum generation from install 
to deploy  o Moved checksum generation into deploy part. Removed checksume from 
   install
     new 6f0ee26  [MSHARED-695] - WIP - Move checksum generation from install 
to deploy  o Moved checksum generation into deploy part. Removed checksum from  
  install.  o Removed it from ProjectInstallerRequest.
     new 92f2a5b  Added debug output.

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   (2287160)
            \
             N -- N -- N   refs/heads/MSHARED-695 (92f2a5b)

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 8 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 | 3 +++
 1 file changed, 3 insertions(+)

-- 
To stop receiving notification emails like this one, please contact
[email protected].

Reply via email to