Note that sometimes not all the versions identified through the “svn log” command appear in this list.That is because when the file is simply moved and not changed or other parts of it were altered, its contents will not be stored in the SVN revision file.
In most cases you will probably realize right away that you just committed something confidential to the SVN repository.
In this case, you only have to fix one single version of that file and is pretty clear which revision is affected.
In other cases, however, the affected file might be in the repository for many revisions before you realize it.
If this is the case, there might be multiple revisions of the file in the repository and each of these versions needs to be fixed.
Version control systems like CVS or Subversion are designed for keeping track of the changes of a project and for having the possibility to revert to old revisions if something goes wrong.
In contrast to regular relational databases, these systems are made only for adding new content to a repository, and not for removing data from it.The incidents of corrupted working copies (causing huge loss of time) and threading-issues just make it almost unusable.Like I mentioned in one of those issues, the loss of time / productivity that we incur because of this broken svn support is just staggering.I'm actively discouraging my colleagues from upgrading to 11.1, and instead prefer them to stay on 11.0 or 10.5.This is very sad, knowing that the Apache Subversion project has released 1.7 almost 1 year ago (October 2011), with very nice improvements like the much faster new working copy format, and IDEA still hasn't gotten proper SVN 1.7 support (and in the meantime it has destabilized SVN support in general, also for 1.6 working copies).If you do not have root access to the repository, you cannot remove any data from the repository! For this example, let’s assume you accidentally committed the file with a plain text password The following commands are performed on your local machine within the working copy of the project, i.e. Before we start tinkering and forging the SVN history and its repository, first fix the affected file and commit a new revision to the repository.