This is an automated email from the ASF dual-hosted git repository.
royteeuwen pushed a change to branch feature/SLING-13253-tally-votes
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-committer-cli.git
discard dfbd8ce SLING-13253 - release tally-votes: PMC-aware result email
omit 53fbee2 SLING-13253 - release update-dist: publish staged artifacts
to dist/release
add 14c3ee7 Merge pull request #29 from apache/feature/SLING-13253-list
add 6f5d818 Merge pull request #30 from
apache/feature/SLING-13253-close-staging
add b772297 Merge pull request #31 from
apache/feature/SLING-13253-promote-drop
add 54790f3 SLING-13253 - release tally-votes: PMC-aware result email
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 (dfbd8ce)
\
N -- N -- N refs/heads/feature/SLING-13253-tally-votes (54790f3)
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:
bnd.bnd | 29 +-
pom.xml | 36 --
.../sling/cli/impl/release/UpdateDistCommand.java | 294 -------------
.../cli/impl/release/UpdateDistCommandTest.java | 462 ---------------------
4 files changed, 1 insertion(+), 820 deletions(-)
delete mode 100644
src/main/java/org/apache/sling/cli/impl/release/UpdateDistCommand.java
delete mode 100644
src/test/java/org/apache/sling/cli/impl/release/UpdateDistCommandTest.java
