without having to remove revisions or create a new repository. I am not responsible for anything that goes wrong because of my description.
It is absolutely necessary to have root access to the SVN respository.
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.
But what happens if you accidentally commit a password or other sensitive information to a repository?
In most cases, people are not going to look in old revisions of a config file, so the faster you commit a new version, the less likely it is that someone sees it!In most cases you will probably realize right away that you just committed something confidential to the SVN repository.