This is an automated email from the ASF dual-hosted git repository.
dklco pushed a change to branch SLING-11069
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-app-cms.git
omit de377301 SLING-11069 - Sync Latest Change from Starter
add 81f795a8 SLING-12138 - Fix login popup in Composum Nodes
add eec5aa93 SLING-12156 - Fix missing oak-segment-tar in composite
features
add 27c3dc1a SLING-12155 - Fix missing maintenance configuration
add 4036e643 SLING-11069 - Sync Latest Change from Starter
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 (de377301)
\
N -- N -- N refs/heads/SLING-11069 (4036e643)
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:
feature/src/main/features/app/composum.json | 21 +++++++++++++++++++++
.../maintenance-config.json} | 2 +-
.../features/oak/node-store/composite-runtime.json | 6 ++++++
.../features/oak/node-store/composite-seed.json | 6 ++++++
4 files changed, 34 insertions(+), 1 deletion(-)
copy feature/src/main/features/{maintenance.json =>
cms/maintenance-config.json} (70%)
