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

slachiewicz pushed a change to branch 
in repository

    omit baa4b8ce Bump org.codehaus.plexus:plexus-interactivity-api from 1.1 to 
     add b24f9719 Bump org.codehaus.plexus:plexus-component-metadata from 2.1.1 
to 2.2.0
     new 6df56dbf Update org.codehaus.plexus:plexus-interactivity-api from 1.1 
to 1.3

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   (baa4b8ce)
             N -- N -- N   

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 1 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 | 16 +---------------
 1 file changed, 1 insertion(+), 15 deletions(-)

Reply via email to