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

michaelo pushed a change to branch maven-3.8.8
in repository https://gitbox.apache.org/repos/asf/maven-site.git


    omit 56ef0d6c Add section for Maven 3.8.x
    omit a9c7a72b Add release notes for Maven 3.8.8
     add b207c206 maven-wrapper-plugin 3.2.0 released
     add 7086db15 links
     add 9f3a79c4 update strategy after #398
     new af5d6725 Add release notes for Maven 3.8.8
     new 6dd371c5 Add section for Maven 3.8.x

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   (56ef0d6c)
            \
             N -- N -- N   refs/heads/maven-3.8.8 (6dd371c5)

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:
 content/apt/developers/compatibility-plan.apt        | 2 ++
 content/apt/guides/mini/guide-maven-classloading.apt | 6 +++---
 content/apt/plugins/index.apt                        | 2 +-
 3 files changed, 6 insertions(+), 4 deletions(-)

Reply via email to