geode-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [geode] branch feature/GEODE-3244 updated (55de597 -> 9b28d87)
Date Mon, 09 Oct 2017 22:59:50 GMT
This is an automated email from the ASF dual-hosted git repository.

zhouxj pushed a change to branch feature/GEODE-3244
in repository

    omit 55de597  GEODE-3244: provide a build in LuceneSerializer that flattens objects
     new 9b28d87  GEODE-3244: provide a build in LuceneSerializer that flattens objects

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   (55de597)
             N -- N -- N   refs/heads/feature/GEODE-3244 (9b28d87)

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.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.

Summary of changes:
 .../serializer => }/      |  45 ++++-
 .../repository/serializer/    |  37 ----
 .../serializer/     |  10 +-
 .../      | 191 ++++++++++++++++-----
 .../serializer/  |   1 +
 .../apache/geode/cache/lucene/test/   |   5 +-
 .../org/apache/geode/cache/lucene/test/ |   9 +-
 7 files changed, 198 insertions(+), 100 deletions(-)
 rename geode-lucene/src/main/java/org/apache/geode/cache/lucene/{internal/repository/serializer
=> }/ (58%)
 delete mode 100644 geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/repository/serializer/

To stop receiving notification emails like this one, please contact
['"" <>'].

View raw message