On Sat, May 11, 2013 at 06:45:03PM +0100, Zé wrote: > You are misrepresenting the problem. It doesn't matter if subversion > isn't like any other SCM system. The problem is that the effect of > copying, renaming or moving a file or directory around, as done by > any SCM system, is incompatible with what's expected out of a > development branch.
That's a matter of definition. Recall that Subversion was designed to be better CVS. It was not designed to be an SCM system that fits anyone's definition of what an SCM system is and what kinds of abstractions it should support. CVS had branches on a per-file level. That alone was deemed insuffient, so Subversion also has branches on a per-directory level. It works well enough this way for many use cases. But of course, it may not work for every use case, and if so people should use a different tool.
