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

slachiewicz pushed a change to branch MSHARED-1003a
in repository https://gitbox.apache.org/repos/asf/maven-archiver.git


 discard 040f40d  [MSHARED-1003] Require Maven 3.2.5+
 discard 2191632  Bump junit to 5.8.3
 discard ceb5e24  [MSHARED-991] small code cleanup
 discard a81608a  Require Maven 3.2.5+
     new 7769e4e  Bump junit to 5.8.3
     new e27143c  [MSHARED-991] small code cleanup
     new a800654  [MSHARED-1003] Require Maven 3.2.5+

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   (040f40d)
            \
             N -- N -- N   refs/heads/MSHARED-1003a (a800654)

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 3 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:

Reply via email to