This is an automated email from the ASF dual-hosted git repository.

zhouxj pushed a change to branch feature/GEODE-6143
in repository https://gitbox.apache.org/repos/asf/geode.git.


 discard fb77417  GEODE-6143: remove PowerMock from 
LuceneEventListenerJUnitTest, fix and add             some test cases.
     add c2c6d35  GEODE-6066: Fixed cluster config update for error case (#2954)
     add 14df491  GEODE-6143: remove PowerMock from 
LuceneEventListenerJUnitTest, fix and add             some test cases.

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   (fb77417)
            \
             N -- N -- N   refs/heads/feature/GEODE-6143 (14df491)

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:
 .../jdbc/internal/cli/CreateDataSourceCommand.java     |  7 +++++--
 .../jdbc/internal/cli/CreateDataSourceCommandTest.java | 18 +++++++-----------
 .../lucene/internal/LuceneEventListenerJUnitTest.java  |  2 +-
 3 files changed, 13 insertions(+), 14 deletions(-)

Reply via email to