[ 
https://issues.apache.org/jira/browse/GEODE-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15852905#comment-15852905
 ] 

ASF GitHub Bot commented on GEODE-2422:
---------------------------------------

GitHub user mmartell opened a pull request:

    https://github.com/apache/geode/pull/391

    GEODE-2422: Switch remaining GemFire strings to Geode.

      - includes rename GemFireCache.hpp to GeodeCache.hpp
      - GemFire, Gemfire, and gemfire replaced with Geode, Geode, geode
      - includes only source changes: .cs, .cpp, and .hpp
      - doesn't include guard statement changes

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mmartell/geode feature/GEODE-2422

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/geode/pull/391.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #391
    
----
commit c6b7d55022fbc7111b93447430d984b95896e688
Author: Mike Martell <mmart...@pivotal.io>
Date:   2017-02-04T19:22:38Z

    GEODE-2422: Switch remaining GemFire strings to Geode.
    
      - includes rename GemFireCache.hpp to GeodeCache.hpp
      - GemFire, Gemfire, and gemfire replaced with Geode, Geode, geode
      - includes only source changes: .cs, .cpp, and .hpp
      - doesn't include guard statement changes

----


> Finish converting from GemFire to Geode in cppcache src
> -------------------------------------------------------
>
>                 Key: GEODE-2422
>                 URL: https://issues.apache.org/jira/browse/GEODE-2422
>             Project: Geode
>          Issue Type: Task
>          Components: native client
>            Reporter: Michael Martell
>
> There are still some classes in the cppcache src that were not converted to 
> Geode from GemFire. For example, GemFireException.
> Also, change corresponding clicache source that uses these.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to