Change Details

There is some small risk here: * overseen call chains which still call the owner and modify the container * other threads might access the same containers, even if class is not designed to be thread-safe, but wrong usages are currently caught mostly by the container copy

There is some small risk here: * overseen call chains which still call the owner and modify the container * other threads might access the same containers, even if class is not designed to be thread-safe, but wrong usages are currently caught mostly by the container copy GIT_SILENT

There is some small risk here: * overseen call chains which still call the owner and modify the container * other threads might access the same containers, even if class is not designed to be thread-safe, but wrong usages are currently caught mostly by the container copy GIT_SILENT