This is an automated email from the ASF dual-hosted git repository.
jsedding pushed a change to branch resolver-2.x-parent-62-and-formatting
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-servlets-resolver.git
discard 2a487eb SLING-12726 ignore spotless code reformatting commit in git
blame
discard ce84059 SLING-12726 apply spotless formatting
discard 5a8bad4 SLING-12726 Update to Parent 62
add 244a9a1 SLING-12726 Update to Parent 62
add f6ac60a SLING-12726 apply spotless formatting
add 20acc40 SLING-12726 ignore spotless code reformatting commit in git
blame
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 (2a487eb)
\
N -- N -- N refs/heads/resolver-2.x-parent-62-and-formatting
(20acc40)
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 | 2 +-
pom.xml | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
