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

haibow pushed a change to branch release-0.4.0-rc3
in repository

 discard 46863b1  [maven-release-plugin] prepare for next development iteration
 discard c3f36c2  [maven-release-plugin] prepare release release-0.4.0-rc3
     new 6ab6d4c  remove distributionManagement
     new 7bcdd1b  [maven-release-plugin] prepare release release-0.4.0-rc3
     new 9c943e3  [maven-release-plugin] prepare for next development iteration

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   (46863b1)
             N -- N -- N   refs/heads/release-0.4.0-rc3 (9c943e3)

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:
 pom.xml | 8 --------
 1 file changed, 8 deletions(-)

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to