IYO: Worst Subversive Mistakes?

Question

What are, in your opinion, the worst tools of subversive (and subversive / cvs-style) errors and what function do you expect / want to use and not there?

thanks:)

edit, I forgot to mention them, for me the main missing functions: - cannot erase what was done earlier; monotony helps to a large extent implementation, but deleting a password will mean resetting the repo, editing the file manually, rebooting the repo (this is not a specific svn error, though) - the metadata here is not very useful. I think that it is impossible to interpolate user-defined properties, effectively search using tags, ... - the client is too free; it is difficult for him to enforce client behavior by administrators. - peer cryptographic authentication (although https or ssh-tunneling help at the network level) - merging operations with a mandatory central repo do not seem to me either fish or flesh:full centralization and strict control or complete decentralization and support of autonomous operations convince me more.

I need to clarify that I am not particularly against svn, it has a lot of good points, but good points are not useful as a starting point for future improvements;)

Answer 1

What I don't like with subversion is that the working copy requires subdirectories .svn.

Answer 2

Calling the beginning and range range of the merge FROM and TO, which always makes people think that it means merging FROM changes where TO merge target, when it really means merging changes that occurred between FROM and TO, and apply them to the working copy.

This makes fusion of pain in other ways.