Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

I'm reading "Professional Team Foundation Server 2010" by Wrox, and in an advantages/disadvantages list, the said:

"Like CVS, SVN makes use of .svn directories inside the source folders to store state of the local working copy, and to allow synchronization with the server. However, it can have the affect of polluting the local source tree, and can cause performance issues wiht very large projects or files."

What does the bit about pollution mean? I've used SVN for C# & ASP.NET projects for a long time and haven't encountered any problems. What probably does this quote think I should have been watching out for?

share|improve this question

migrated from stackoverflow.com Jul 11 '12 at 14:13

This question came from our site for professional and enthusiast programmers.

add comment

1 Answer

up vote 11 down vote accepted

"Polluting the source tree" is the term they're using to mean that SVN places hidden directories (.svn directories) throughout your source code. The .svn directories contain metadata regarding your checked-out source code. Traditionally, there has been a one-to-one correspondence between a directory in your source code and a corresponding .svn directory. Therefore, bigger source code, more .svn directories.

Actually, SVN 1.7 drastically changes (for the better) how this process works. Now, there is only one .svn directory for your entire working copy. I don't think this "polluting" is a fair criticism any longer.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.