I've recently been discussing using Subversion as our primary source
control system at the company where I work and I've been given the ok to
go ahead and set it up after running some successful tests on my local
box, using TortoiseSVN as our primary access method.
I noticed in the FAQ that there can be a problem with web applications
and the .svn folder name, and I was wondering if someone could tell me
what the problem is and what causes it in a bit more detail. It was a
concern to me as we have been working on a number of large web
applications that we need source control for but I have tested using
subversion with our web apps, and publishing them from my local dev box
to the pre-production server whilst they are under source control and
there doesn't seem to be a problem at all that I can see.
I ask because it would be hard to justify using Subversion if we have to
change our workflow significantly, or use a custom version of the
clients (using _svn instead of .svn) to do it. The custom client is out
because another division in the company already uses subversion and we
need to maintain cross compatibility.
They have told me that they havn't come across any problems either, are
we missing something?
Received on Fri Jan 14 03:07:56 2005