This is an automated email from the ASF dual-hosted git repository.
royteeuwen pushed a change to branch feature/SLING-13253-site-shallow-clone
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-committer-cli.git
omit 70bad41 SLING-13253 - update-local-site: shallow-clone the site
checkout
add 3abc65e SLING-13289 - complete the Docker image rename
add e2a0d70 Merge pull request #51 from
apache/feature/SLING-13289-complete-image-rename
add 597a042 Merge pull request #50 from
apache/feature/SLING-13253-site-update-fixes
add d59f659 SLING-13253 - update-local-site: shallow-clone the site
checkout
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 (70bad41)
\
N -- N -- N refs/heads/feature/SLING-13253-site-shallow-clone
(d59f659)
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:
README.md | 2 +-
run.sh | 2 +-
src/main/java/org/apache/sling/cli/impl/CommandProcessor.java | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
