I'm new on CLion and before I used to rely on atomic svn commit.
I just had to cancel my commit in CLion. Locally, it seems that nothing was committed but when I committed again, svn said that some files were out of date. Actually those files had been committed but the working copy said they were not. After an update and another commit all was ok but during some minutes, the repo was not good because some changes were missing.
I don't understand how CLion could do that because it uses the svn command line tool but I have never had this problem using svn command line tool.
Is there really any chances CLion induces this problem?