This is an automated email from the ASF dual-hosted git repository.
jsinovassinnaik pushed a change to branch UNOMI-885
in repository https://gitbox.apache.org/repos/asf/unomi.git
discard 038fc7d22 UNOMI-885: update test to check rollover indices after
migration
discard d82b5e2c5 UNOMI-885: change rollover value to have more than one
rollover index after migration
discard 7b10d821a UNOMI-885: fix migration error on rollover alias
add f0624a5ed UNOMI-885: fix migration error on rollover alias
add a3be1199a UNOMI-885: change rollover value to have more than one
rollover index after migration
add f2d7cd439 UNOMI-885: update test to check rollover indices after
migration
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 (038fc7d22)
\
N -- N -- N refs/heads/UNOMI-885 (f2d7cd439)
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:
.../org/apache/unomi/shell/migration/utils/MigrationUtils.java | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
