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

emilles pushed a change to branch GROOVY-11841
in repository https://gitbox.apache.org/repos/asf/groovy.git


 discard a75e87f122 remove boundless property name map
 discard bebc51f327 GROOVY-11841: use `ConcurrentHashMap` for mutable property 
index maps
     new 19f011936b remove boundless property name map
     new db96c92851 GROOVY-11841: use `ConcurrentHashMap` for mutable property 
index maps

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   (a75e87f122)
            \
             N -- N -- N   refs/heads/GROOVY-11841 (db96c92851)

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:
 src/main/java/groovy/lang/MetaClassImpl.java | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Reply via email to