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

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


 discard 076d784  Merge branch 'feature/GEODE-Lucene-Udo' of 
github.com:apache/geode into feature/GEODE-5096
    omit e08268a  Lucene excluding Exception 
sanctioned-geode-core-serializables.txt
    omit 41bbaeb  GEODE-lucene amended tests
    omit 0a43edb  Initial commit
    omit 49991b3  GEODE-5077: Categorized newly added oql tests (#1797)
 discard 9bf4545  Lucene excluding Exception 
sanctioned-geode-core-serializables.txt
 discard 31a7f28  GEODE-lucene amended tests
 discard b6a75db  Initial commit
     new cc798b9  GEODE-5096: Added support to validate server cache profiles 
in the case of concurrent updates to region cache profiles.
     new 73ece1f  GEODE-5077: Categorized newly added oql tests (#1797)

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   (076d784)
            \
             N -- N -- N   refs/heads/feature/GEODE-5096 (73ece1f)

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 2 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:
 .../test/resources/org/apache/geode/codeAnalysis/excludedClasses.txt   | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

-- 
To stop receiving notification emails like this one, please contact
[email protected].

Reply via email to