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

kwin pushed a change to branch feature/update-parent
in repository 
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-servlets-annotations.git


 discard 57d4854  SLING-12968 Apply code formatting
 discard d52095a  SLING-12968 Update to Parent 62
     add 5138a36  Merge pull request #5 from apache/feature/update-parent
     add 147c7f2  SLING-12094 - Use GitHub for the Maven scm.url value
     add 3f4b053  SLING-12459 - Redirect sonarcloud notifications to 
[email protected]
     add 447c35a  SLING-12866 - Restrict force pushes, auto-delete branches on 
merge
     add d4ab0b5  SLING-12968 Update to Parent 62
     add 28e3391  SLING-12968 Apply code formatting

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   (57d4854)
            \
             N -- N -- N   refs/heads/feature/update-parent (28e3391)

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.

No new revisions were added by this update.

Summary of changes:
 .asf.yaml | 5 +++++
 pom.xml   | 2 +-
 2 files changed, 6 insertions(+), 1 deletion(-)

Reply via email to