Tortoise svn error validating server certificate
Subversion is equally efficient on binary as on text files, because it uses a binary diffing algorithm to transmit and store successive revisions.(SVN wins, but size is not a huge problem these days and SVN repositories are almost 2x CVS repositories)In general, the time required for a Subversion operation is proportional to the size of the changes resulting from that operation, not to the absolute size of the project in which the changes are taking place.Actually, it turns out that we can use these properties in Kepler to place a dependency on the pt II svn tree so that when a user checks out the kepler svn tree, they can automatically check out the pt II svn tree.This is a case of vendor lock-in, but does give SVN an advantage.As I mentioned early I've been working on a SVN post-commit script.We've got a SVN repository that will be modified by several remote developers and I really need to keep an eye on this repository and I need to closely monitor changes to this repository.Subversion has since expanded beyond its original goal of replacing CVS, but its history influenced its feature and interface choices; Subversion today should still feel very familiar to CVS users.Subversion allows arbitrary metadata ("properties") to be attached to any file or directory.
Revision numbers are per-commit, not per-file, and commit's log message is attached to its revision, not stored redundantly in all the files affected by that commit.
There is no reason for these operations to be expensive, so they aren't.