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

ASF GitHub Bot commented on MNEMONIC-20:
----------------------------------------

GitHub user bigdata-memory opened a pull request:

    https://github.com/apache/incubator-mnemonic/pull/14

    MNEMONIC-20: Formalize the names of annotations, classes and methods

    

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

    $ git pull https://github.com/NonVolatileComputing/incubator-mnemonic master

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

    https://github.com/apache/incubator-mnemonic/pull/14.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 #14
    
----
commit 679bcdc151213ca4e1bf57cd6cebddd2ae36841c
Author: Wang, Gang(Gary) <gang1.w...@intel.com>
Date:   2016-04-14T01:28:35Z

    MNEMONIC-20: Formalize the names of annotations, classes and methods

commit 1e75e2a52cfde1ccfa6e0b062da20373be204ad2
Author: Wang, Gang(Gary) <gang1.w...@intel.com>
Date:   2016-04-14T01:36:34Z

    fix the name of VolatileAllocatorNGTest, changed to 
VolatileMemAllocatorNGTest

----


> Formalize the names of annotations, classes and methods
> -------------------------------------------------------
>
>                 Key: MNEMONIC-20
>                 URL: https://issues.apache.org/jira/browse/MNEMONIC-20
>             Project: Mnemonic
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Wang, Gang
>            Assignee: Wang, Gang
>
> Mnemonic is using annotation @NonVolatileEntity to mark durable class, 
> however, this name doesn't well describe the behaviors of durable object very 
> accurately, so it will be renamed to @DurabeEntity, There are some other 
> class, method, names should be renamed as well for the purpose of consistency



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to