Friday, July 20, 2012

#looks like SVN had a little bit of a re-design...

SVN has its uses, but i was never a big fan due to some of the apparent sync issues when multiple people have to work on the same project and especially when the project becomes larger. not to mention that SVN branches are out of the question for most developers. one strictly annoying thing though, was the per-folder localized database instead of a centralised database per repository, which seem they redesigned in 1.7.0 (from october 2011 - yep, haven't used it for a while):

A key feature of the changes introduced in Subversion 1.7 is the centralization of working copy metadata storage into a single location. Instead of a .svn directory in every directory in the working copy, Subversion 1.7 working copies have just one .svn directory—in the root of the working copy. This directory includes (among other things) an SQLite-backed database which contains all of the metadata Subversion needs for that working copy.