This is an automated email from the ASF dual-hosted git repository.
sseifert pushed a change to branch feature/SLING-12281-parent-60
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-contentparser-api.git
omit f507a4e SLING-12281 limit build to java 17 and 21
omit 3ed1c0a SLING-12281 ignore spotless code reformatting commit in git
blame
omit af40e87 SLING-12281 apply spotless code formatting
omit 76ac52f SLING-12281 Update to Parent 60, Java 11 Minimum Version
add e6450e6 SLING-12281 Update to Parent 60, Java 11 Minimum Version
add 6339820 SLING-12281 apply spotless 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 (f507a4e)
\
N -- N -- N refs/heads/feature/SLING-12281-parent-60 (6339820)
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:
.git-blame-ignore-revs | 1 -
1 file changed, 1 deletion(-)
delete mode 100644 .git-blame-ignore-revs
