This is an automated email from the ASF dual-hosted git repository.
royteeuwen pushed a change to branch feature/SLING-13253-finalize-site-update
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-committer-cli.git
omit 971fa2b SLING-13253 - update-local-site: trim the
updateDownloadsByArtifactId javadoc
omit eaa5dc5 SLING-13253 - update-local-site: drop the superseded
name-based matching
omit e69033c SLING-13253 - finalize: update the Sling website as the last
step
add 349c3ba SLING-13253 - finalize: update the Sling website as the last
step
add 6755a6b SLING-13253 - update-local-site: drop the superseded
name-based matching
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 (971fa2b)
\
N -- N -- N refs/heads/feature/SLING-13253-finalize-site-update
(6755a6b)
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:
