This is an automated email from the ASF dual-hosted git repository.
rombert pushed a change to branch issue/SLING-12029
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-feature-extension-content.git
discard e984fa3 trivial: code cleanups
discard 646aa27 SLING-12029 - Make strictMode configurable
omit 6db6241 Update to the latest version of the parent POM
omit 56cd1fc SLING-12028 - Content Deployment Extension tests fail on
Windows
add d8ad58f SLING-12028 - Content Deployment Extension tests fail on
Windows
add 9c4d4f0 Update to the latest version of the parent POM
new e678ce6 SLING-12029 - Make strictMode configurable
new ffd77b3 trivial: code cleanups
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 (e984fa3)
\
N -- N -- N refs/heads/issue/SLING-12029 (ffd77b3)
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 2 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:
